Triple
T11005293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YUC |
E260101
|
entity |
| Predicate | associatedSubdivision |
P66180
|
FINISHED |
| Object | federal entity of Yucatán |
—
|
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: federal entity of Yucatán | Statement: [YUC, associatedSubdivision, federal entity of Yucatán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSubdivision Context triple: [YUC, associatedSubdivision, federal entity of Yucatán]
-
A.
associatedWithSubdivision
chosen
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
-
B.
formerSubdivisionOf
Indicates that an entity once functioned as an administrative or territorial part of another entity but no longer holds that status.
-
C.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
D.
primarySubdivisionOf
Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic entity.
-
E.
associatedCountrySubdivisionCode
Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.