Triple
T13784809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-485 |
E331225
|
entity |
| Predicate | hasLoopRole |
P111452
|
FINISHED |
| Object | outer circumferential route for Charlotte |
—
|
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: outer circumferential route for Charlotte | Statement: [I-485, hasLoopRole, outer circumferential route for Charlotte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoopRole Context triple: [I-485, hasLoopRole, outer circumferential route for Charlotte]
-
A.
hasLoopMode
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
hasLoopDirectionOptions
Indicates that an entity provides or supports multiple possible directions in which a loop can operate or be executed.
-
D.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
-
E.
hasBusLoop
Indicates that a location or facility includes a designated looped roadway or area specifically for bus circulation, stopping, or turning.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.