Triple
T3019479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gtech Community Stadium |
E82418
|
entity |
| Predicate | distanceFromPredecessor |
P44655
|
FINISHED |
| Object | approximately 1 mile |
—
|
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: approximately 1 mile | Statement: [Gtech Community Stadium, distanceFromPredecessor, approximately 1 mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPredecessor Context triple: [Gtech Community Stadium, distanceFromPredecessor, approximately 1 mile]
-
A.
predecessorLocatedAt
Indicates that the location specified was the place where the immediately preceding version, state, or instance of an entity was situated.
-
B.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
C.
distanceToSuccessorStadium
Indicates the measured distance between a stadium and the stadium that directly succeeds it in a defined sequence or timeline.
-
D.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
E.
predecessorState
Indicates that one state directly precedes another in a sequence or process.
- F. None of above. chosen
Provenance (4 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a927b608190ba1392498507b237 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.