Triple
T36699845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Víctor Romo |
E906194
|
entity |
| Predicate | capitalOfPoliticalActivity |
P193672
|
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: [Víctor Romo, capitalOfPoliticalActivity, Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfPoliticalActivity Context triple: [Víctor Romo, capitalOfPoliticalActivity, Mexico City]
-
A.
capitalOfActivity
chosen
Indicates that a location serves as the primary center or hub where a particular activity is concentrated or predominantly carried out.
-
B.
isPrimaryPoliticalHubOf
Indicates that a location serves as the main center of political authority, administration, or governance for the referenced entity.
-
C.
politicalActivityRegion
Indicates the geographic region or area in which a political activity takes place or is focused.
-
D.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
E.
capitalCityGoverningFrom
Indicates that a specified capital city serves as the administrative center from which a given political entity is governed.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:12 p.m.