Triple
T29620470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City–Laredo corridor |
E754980
|
entity |
| Predicate | startPointCountryCapital |
P135986
|
FINISHED |
| Object | Mexico City |
—
|
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: Mexico City | Statement: [Mexico City–Laredo corridor, startPointCountryCapital, Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPointCountryCapital Context triple: [Mexico City–Laredo corridor, startPointCountryCapital, Mexico City]
-
A.
startPointIsCapitalOf
chosen
Indicates that the starting point in a relation or path is a city that serves as the capital of the relevant region, country, or administrative entity.
-
B.
homeCountryCapital
Indicates that a given city is the capital of a specified country that serves as an entity’s home or origin.
-
C.
associatedCountryCapital
Indicates that a country is related to, or paired with, its capital city.
-
D.
hostCountryCapitalOf
Indicates that a country serves as the capital-hosting nation for a specified city or capital entity.
-
E.
modernCountryOfCapital
Indicates that a given city serves as the capital of a specified modern-day country.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 28, 2026, 6:34 p.m.