Triple

T22640586
Position Surface form Disambiguated ID Type / Status
Subject Mexican Federal Highway 80 E558812 entity
Predicate connectsInlandTo P129446 FINISHED
Object Pacific coast of Mexico 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: Pacific coast of Mexico | Statement: [Mexican Federal Highway 80, connectsInlandTo, Pacific coast of Mexico]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsInlandTo
Context triple: [Mexican Federal Highway 80, connectsInlandTo, Pacific coast of Mexico]
  • A. connectsInlandRoutesTo
    Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
  • B. connectsInlandToBorder
    Indicates that an inland location is linked or provides a route to a border location.
  • C. connectsInlandCommunitiesTo
    Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
  • D. connectsInlandCityToCoast
    Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
  • E. connectsCoastToInland chosen
    Indicates a relationship where something (such as a route, structure, or feature) links a coastal area to an inland area.
  • 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_69e24547f7fc819086e2c4ba3b979657 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f170116fe881908178cffef26e3ae7 completed April 29, 2026, 2:42 a.m.
PD Predicate disambiguation batch_69ee6294c4c08190b7e4829f4b9af24b completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:04 p.m.