Triple

T10573559
Position Surface form Disambiguated ID Type / Status
Subject Mexico City–Acapulco corridor E249552 entity
Predicate hasEndpointCharacteristic P274 FINISHED
Object national capital 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: national capital | Statement: [Mexico City–Acapulco corridor, hasEndpointCharacteristic, national capital]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEndpointCharacteristic
Context triple: [Mexico City–Acapulco corridor, hasEndpointCharacteristic, national capital]
  • A. hasCharacteristic chosen
    Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
  • B. hasEndpointType
    Indicates that an entity has a specific type or classification assigned to one of its endpoints.
  • C. hasEndpointStation
    Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
  • D. eraCharacteristic
    Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
  • E. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5274929cc81909a79d5e2049f7389 completed April 7, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69d51901ff6c819095e7b528170a69dc completed April 7, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:37 p.m.