Triple
T6172961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indy NXT |
E137746
|
entity |
| Predicate | ladderPosition |
P64522
|
FINISHED |
| Object | top rung of the Road to Indy-style ladder system |
—
|
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: top rung of the Road to Indy-style ladder system | Statement: [Indy NXT, ladderPosition, top rung of the Road to Indy-style ladder system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ladderPosition Context triple: [Indy NXT, ladderPosition, top rung of the Road to Indy-style ladder system]
-
A.
positionOfLDP
Indicates the spatial or geometric location of a local datum point (LDP) relative to a defined reference or coordinate system.
-
B.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
classPosition
chosen
Indicates the relative ordering or rank of an entity within a class, group, 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d9319548190980c99f692bd4115 |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.