Triple
T26176762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IY |
E654563
|
entity |
| Predicate | canBeLoadedByInstruction |
P127767
|
FINISHED |
| Object | LD IY,nn |
—
|
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 IY,nn | Statement: [IY, canBeLoadedByInstruction, LD IY,nn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeLoadedByInstruction Context triple: [IY, canBeLoadedByInstruction, LD IY,nn]
-
A.
canBeLoadedBy
chosen
Indicates that one entity is capable of being loaded, initialized, or brought into use by another entity.
-
B.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
C.
hasInstructionCache
Indicates that an entity possesses or is equipped with an instruction cache for storing and accessing executable instructions.
-
D.
usedByInstruction
Indicates that something (such as a resource, value, or object) is utilized or referenced by a particular instruction.
-
E.
hasInstructionModel
Indicates that one entity is associated with, or utilizes, a specific instruction-oriented model to guide its behavior or processing.
- 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_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 26, 2026, 8:38 p.m.