Triple
T9672596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 214 (unused number) |
E234064
|
entity |
| Predicate | isSpurOrLoop |
P3377
|
FINISHED |
| Object | no designated function |
—
|
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: no designated function | Statement: [Interstate 214 (unused number), isSpurOrLoop, no designated function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpurOrLoop Context triple: [Interstate 214 (unused number), isSpurOrLoop, no designated function]
-
A.
isSpurOf
chosen
Indicates that one entity is a secondary offshoot, branch, or derivative extension originating from another primary entity.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
isOnLoopSide
Indicates that one entity is located on the side or segment of a loop structure relative to another reference point or element.
-
D.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
-
E.
isOnLoopLine
Indicates that one entity (typically a route, track, or segment) lies on or belongs to a loop-shaped line or circuit within a network.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.