Triple
T25366927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Cayenne |
E632824
|
entity |
| Predicate | ianaDatabaseZoneId |
P6294
|
FINISHED |
| Object | America/Cayenne |
—
|
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/Cayenne | Statement: [America/Cayenne, ianaDatabaseZoneId, America/Cayenne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ianaDatabaseZoneId Context triple: [America/Cayenne, ianaDatabaseZoneId, America/Cayenne]
-
A.
timeZoneArea
Indicates the geographic area or region for which a particular time zone is defined or applicable.
-
B.
ianaTimeZoneId
chosen
Indicates the association between an entity and its time zone as identified by a standard IANA time zone identifier (e.g., "America/New_York").
-
C.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
D.
javaTimeZoneID
Indicates that an entity is associated with a specific Java time zone identifier (e.g., "America/New_York") used for date and time operations.
-
E.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10eb1748190aa576850282c808d |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:37 p.m.