Triple
T31483391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacubaya, Mexico City |
E803205
|
entity |
| Predicate | integratedIntoMexicoCity |
P177584
|
FINISHED |
| Object | 19th–20th centuries |
—
|
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: 19th–20th centuries | Statement: [Tacubaya, Mexico City, integratedIntoMexicoCity, 19th–20th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoMexicoCity Context triple: [Tacubaya, Mexico City, integratedIntoMexicoCity, 19th–20th centuries]
-
A.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
B.
sharesTemploMayorWith
Indicates that two entities are associated with, located at, or share a connection through the same Templo Mayor site.
-
C.
isWalledCityNorthOfMexico
Indicates that a walled city is located geographically to the north of Mexico.
-
D.
locatedInDirectionFromMexicoCityCenter
Indicates the relative compass direction in which one place is situated from the center of Mexico City.
-
E.
integratedIntoParis
Indicates that one entity has been incorporated or merged into the administrative, social, or structural framework of Paris.
- F. None of above. chosen
Provenance (4 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 30, 2026, 9:33 p.m.