Triple
T35429936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Cancun |
E1024027
|
entity |
| Predicate | legalTimeZoneOfState |
P103458
|
FINISHED |
| Object | Quintana Roo |
—
|
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: Quintana Roo | Statement: [America/Cancun, legalTimeZoneOfState, Quintana Roo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTimeZoneOfState Context triple: [America/Cancun, legalTimeZoneOfState, Quintana Roo]
-
A.
countryTimeStandardFor
Indicates that a specific time standard (such as a time zone or time-keeping system) is officially used by a given country.
-
B.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
C.
zoneRequirement
Indicates that a certain condition, constraint, or prerequisite must be satisfied within a specified zone or area.
-
D.
timeZoneState
chosen
Indicates that one entity is a state or region associated with the time zone of another entity.
-
E.
isSubnationalTimeZoneOf
Indicates that a time zone is officially used within, and is a subdivision-specific part of, a particular country or larger political 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:03 p.m.