Triple
T7296475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archie |
E164533
|
entity |
| Predicate | inComputingDomain |
P20866
|
FINISHED |
| Object | information retrieval |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: information retrieval | Statement: [Archie, inComputingDomain, information retrieval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inComputingDomain Context triple: [Archie, inComputingDomain, information retrieval]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
usedInComputerScience
chosen
Indicates that something is applied, referenced, or has practical relevance within the field of computer science.
-
C.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
D.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
E.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.