Triple
T4393746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaSalle/Van Buren |
E99429
|
entity |
| Predicate | loopDirectionServed |
P30562
|
FINISHED |
| Object | counter-clockwise Inner Loop |
—
|
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: counter-clockwise Inner Loop | Statement: [LaSalle/Van Buren, loopDirectionServed, counter-clockwise Inner Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopDirectionServed Context triple: [LaSalle/Van Buren, loopDirectionServed, counter-clockwise Inner Loop]
-
A.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
B.
hasLoopDirectionOptions
Indicates that an entity provides or supports multiple possible directions in which a loop can operate or be executed.
-
C.
servesDirection
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
D.
hasCountingDirection
Indicates the direction or order in which counting or enumeration proceeds between related entities.
-
E.
circuitDirection
chosen
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.