Triple
T4785632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 12E |
E106469
|
entity |
| Predicate | routeShape |
P20601
|
FINISHED |
| Object | 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: loop | Statement: [Route 12E, routeShape, loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeShape Context triple: [Route 12E, routeShape, loop]
-
A.
routeSymbolShape
chosen
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
routeStructure
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
-
D.
routeDescription
Indicates a textual explanation or summary of the path, course, or itinerary taken between locations.
-
E.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65b0ea408190b348d917883381de |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.