Triple
T31018607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico |
E790391
|
entity |
| Predicate | includesFederalEntity |
P7371
|
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, includesFederalEntity, Mexico City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFederalEntity Context triple: [Mexico, includesFederalEntity, Mexico City]
-
A.
federalEntityInvolved
Indicates that a federal-level government body or authority is involved in, associated with, or has jurisdiction over the referenced action or relationship.
-
B.
includesFederalMemberState
Indicates that an entity (such as a federation or union) has a particular member state as part of its federal structure.
-
C.
includesFederalDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a federal district within its boundaries.
-
D.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
E.
includesFederalState
Indicates that one entity encompasses or contains both federal-level and state-level components, jurisdictions, or elements.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: April 29, 2026, 8:58 p.m.