Triple
T33135512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monroe, Louisiana Metropolitan Statistical Area |
E847992
|
entity |
| Predicate | containsMajorHighway |
P385
|
FINISHED |
| Object | U.S. Route 165 |
—
|
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 165 | Statement: [Monroe, Louisiana Metropolitan Statistical Area, containsMajorHighway, U.S. Route 165]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMajorHighway Context triple: [Monroe, Louisiana Metropolitan Statistical Area, containsMajorHighway, U.S. Route 165]
-
A.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
B.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
D.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
E.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 1, 2026, 1:27 a.m.