Triple
T15797473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciudad Cuauhtémoc–La Mesilla border crossing |
E383017
|
entity |
| Predicate | hasModeOfCrossing |
P10712
|
FINISHED |
| Object | road |
—
|
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: road | Statement: [Ciudad Cuauhtémoc–La Mesilla border crossing, hasModeOfCrossing, road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeOfCrossing Context triple: [Ciudad Cuauhtémoc–La Mesilla border crossing, hasModeOfCrossing, road]
-
A.
crossingType
chosen
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
hasMethodOfCrossing
Indicates that one entity uses or is associated with a particular way or technique of crossing another entity or obstacle.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4def80481908f72733ce9133bc6 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.