Triple
T32220021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Standard Time (Mexico) |
E823037
|
entity |
| Predicate | IANAZone |
P128587
|
FINISHED |
| Object | America/Cancun |
—
|
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: America/Cancun | Statement: [Eastern Standard Time (Mexico), IANAZone, America/Cancun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IANAZone Context triple: [Eastern Standard Time (Mexico), IANAZone, America/Cancun]
-
A.
ianaZoneFile
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
B.
DNSZone
Indicates a relationship where a set of DNS records is grouped and managed together under a specific domain namespace as a single administrative unit.
-
C.
hasIANAZone
chosen
Indicates that an entity is associated with, or mapped to, a specific IANA time zone identifier.
-
D.
IANAStatus
Indicates the current registration or assignment status of an Internet resource as recorded by the Internet Assigned Numbers Authority (IANA).
-
E.
ICANNRootZoneManagedBy
Indicates that the management and administrative control of a given DNS root zone is carried out by ICANN.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc4129481909d12bf4d5723dd3b |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.