Triple
T5032440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Corners, Maryland |
E113337
|
entity |
| Predicate | majorRoadJunction |
P37486
|
FINISHED |
| Object | U.S. Route 29 |
—
|
NE NERFINISHED |
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: U.S. Route 29 | Statement: [Four Corners, Maryland, majorRoadJunction, U.S. Route 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoadJunction Context triple: [Four Corners, Maryland, majorRoadJunction, U.S. Route 29]
-
A.
isMajorRoadJunction
chosen
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
B.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
C.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
D.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b4d1708190aa1fa63104555f8a |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.