Triple
T26176768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IY |
E654563
|
entity |
| Predicate | usedInInstructionForm |
P168560
|
FINISHED |
| Object | LD r,(IY+d) |
—
|
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: LD r,(IY+d) | Statement: [IY, usedInInstructionForm, LD r,(IY+d)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInInstructionForm Context triple: [IY, usedInInstructionForm, LD r,(IY+d)]
-
A.
usedByInstruction
chosen
Indicates that something (such as a resource, value, or object) is utilized or referenced by a particular instruction.
-
B.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
-
C.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
D.
usedInFormat
Indicates that something (such as a method, standard, or component) is employed or applied within a particular format.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 26, 2026, 8:38 p.m.