Triple
T27612429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetResponse-PDU |
E700359
|
entity |
| Predicate | errorIndexRefersTo |
P86300
|
FINISHED |
| Object | position of failing variable binding |
—
|
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: position of failing variable binding | Statement: [GetResponse-PDU, errorIndexRefersTo, position of failing variable binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorIndexRefersTo Context triple: [GetResponse-PDU, errorIndexRefersTo, position of failing variable binding]
-
A.
errorIndexSemantics
chosen
Indicates the position or index within a sequence or structure at which a semantic error occurs or is identified.
-
B.
associatedIndex
Indicates that one entity is linked to another through a corresponding index or positional reference.
-
C.
isReferenceIndexFor
Indicates that one entity serves as an index or pointer used to locate, identify, or access another entity.
-
D.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
-
E.
indexEquals
Indicates that two elements or positions share the same index within an ordered structure or sequence.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:11 p.m.