Triple
T35429954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Cancun |
E1024027
|
entity |
| Predicate | introducedAsSeparateZone |
P47209
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [America/Cancun, introducedAsSeparateZone, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsSeparateZone Context triple: [America/Cancun, introducedAsSeparateZone, 2015]
-
A.
otherZones
Indicates that an entity is associated with or belongs to zones that are distinct from a primary or reference zone.
-
B.
separatedRegion
Indicates that one region is distinct from and not contiguous with another region, with a clear separation between them.
-
C.
separatedAsRegion
chosen
Indicates that one entity is distinguished or partitioned from others as a distinct region or area.
-
D.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
E.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
- 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_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:03 p.m.