Triple
T26176766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IY |
E654563
|
entity |
| Predicate | canBePoppedByInstruction |
P168560
|
FINISHED |
| Object | POP IY |
—
|
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: POP IY | Statement: [IY, canBePoppedByInstruction, POP IY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePoppedByInstruction Context triple: [IY, canBePoppedByInstruction, POP IY]
-
A.
canBePoppedFromStack
Indicates that an element is eligible to be removed from the top of a stack data structure.
-
B.
canBePushedToStack
Indicates that an entity is eligible to be placed onto a stack data structure.
-
C.
hasTypeOfInstruction
Indicates that one entity specifies, assigns, or is associated with a particular type or category of instruction for another entity.
-
D.
usedByInstruction
chosen
Indicates that something (such as a resource, value, or object) is utilized or referenced by a particular instruction.
-
E.
basedOnInstructionFrom
Indicates that an action or decision is carried out according to, or derived from, a specific instruction given by another entity.
- 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_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 8:38 p.m.