Triple
T29631489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific/Tahiti |
E755582
|
entity |
| Predicate | observesSingleOffsetAllYear |
P136721
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pacific/Tahiti, observesSingleOffsetAllYear, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesSingleOffsetAllYear Context triple: [Pacific/Tahiti, observesSingleOffsetAllYear, true]
-
A.
observesSingleTimeAllYear
Indicates that an entity observes or performs the referenced action exactly once during the entire year.
-
B.
observesAllYear
Indicates that the observing entity continuously observes or monitors the target entity throughout the entire year without interruption.
-
C.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
-
D.
offsetFromUTCAllYear
chosen
Indicates that the time-related entity maintains a constant, unchanging offset from Coordinated Universal Time (UTC) throughout the entire year, without seasonal adjustments such as daylight saving time.
-
E.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 6:41 p.m.