Triple
T36076900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEX 45D |
E1043519
|
entity |
| Predicate | parallelRouteClass |
P19597
|
FINISHED |
| Object | libre |
—
|
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: libre | Statement: [MEX 45D, parallelRouteClass, libre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelRouteClass Context triple: [MEX 45D, parallelRouteClass, libre]
-
A.
parallelRoute
chosen
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
B.
parallelClass
Indicates that two or more classes or groups exist at the same level and operate concurrently or in a comparable, non-intersecting manner.
-
C.
connectedRoute
Indicates that there is a direct or logically continuous path linking two locations or segments within a network.
-
D.
standardRouteClass
Indicates that a route is classified according to a predefined standard category or class used for routing or transportation.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.