Triple
T36878235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicxulbeño |
E911401
|
entity |
| Predicate | stateOfAssociatedPlace |
P88409
|
FINISHED |
| Object | Yucatán |
—
|
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: Yucatán | Statement: [Chicxulbeño, stateOfAssociatedPlace, Yucatán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfAssociatedPlace Context triple: [Chicxulbeño, stateOfAssociatedPlace, Yucatán]
-
A.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
-
B.
associatedProvinceOrState
chosen
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
-
C.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
D.
governingStateAssociation
Indicates a relationship where one entity serves as the governing state or authority responsible for overseeing, regulating, or administering another entity.
-
E.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: May 3, 2026, 4:13 p.m.