Triple
T33263017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinichná |
E851571
|
entity |
| Predicate | linkedPoliticalCenter |
P30675
|
FINISHED |
| Object | Dzibanché |
—
|
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: Dzibanché | Statement: [Kinichná, linkedPoliticalCenter, Dzibanché]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedPoliticalCenter Context triple: [Kinichná, linkedPoliticalCenter, Dzibanché]
-
A.
politicalCenterType
Indicates the type or classification of a political center associated with an entity.
-
B.
deFactoPoliticalCenter
Indicates that a location functions as the practical or informal center of political power or administration, even if it is not officially designated as such.
-
C.
politicalCenterDuring
Indicates that an entity serves as the primary political center or seat of political authority for another entity during a specified time period.
-
D.
linkedPolities
Indicates that two political entities are connected by some defined relationship, such as alliance, dependency, or shared governance.
-
E.
isPrimaryPoliticalHubOf
chosen
Indicates that a location serves as the main center of political authority, administration, or governance for the referenced 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:32 a.m.