Triple
T20002251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnum Island |
E494361
|
entity |
| Predicate | hasPrimaryTimezoneAbbreviation |
P67797
|
FINISHED |
| Object | EST |
—
|
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: EST | Statement: [Barnum Island, hasPrimaryTimezoneAbbreviation, EST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTimezoneAbbreviation Context triple: [Barnum Island, hasPrimaryTimezoneAbbreviation, EST]
-
A.
includesTimeZoneAbbreviation
chosen
Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
-
B.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
C.
hasStandardTimeZone
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
D.
hasStandardTimeUTCOffset
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
-
E.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a2e34481908a495cc5d077c41f |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.