Triple
T24331279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autopista México–Acapulco |
E613250
|
entity |
| Predicate | hasMajorJunctionNear |
P31669
|
FINISHED |
| Object | Cuernavaca |
—
|
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: Cuernavaca | Statement: [Autopista México–Acapulco, hasMajorJunctionNear, Cuernavaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorJunctionNear Context triple: [Autopista México–Acapulco, hasMajorJunctionNear, Cuernavaca]
-
A.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
B.
nearJunctionOf
chosen
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.
-
C.
isMajorJunctionOnLine
Indicates that a location serves as a primary connecting junction along a particular line or route.
-
D.
hasMajorRailCrossing
Indicates that there is a significant railway crossing (such as a major rail line intersecting a road or another transport route) at or associated with the referenced location or entity.
-
E.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f1312081909d44baa1e296c735 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:55 a.m.