Triple
T26123480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of Mexico |
E659037
|
entity |
| Predicate | capitalIncluded |
P164820
|
FINISHED |
| Object | Ciudad de México |
—
|
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: Ciudad de México | Statement: [States of Mexico, capitalIncluded, Ciudad de México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalIncluded Context triple: [States of Mexico, capitalIncluded, Ciudad de México]
-
A.
chargesIncluded
Indicates that the specified charges or fees are already accounted for and included within the referenced amount or agreement.
-
B.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
C.
countryIncludes
Indicates that a country geographically or administratively contains or encompasses a specified region, territory, or subdivision.
-
D.
coversCapital
Indicates that one entity provides coverage, service, or applicability specifically to the capital city of another entity.
-
E.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 8:10 p.m.