Triple
T29631488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific/Tahiti |
E755582
|
entity |
| Predicate | isHistoricalZone |
P1832
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Pacific/Tahiti, isHistoricalZone, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricalZone Context triple: [Pacific/Tahiti, isHistoricalZone, false]
-
A.
timeZoneHistorical
chosen
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
-
B.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
C.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
D.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
E.
isHistoricFor
Indicates that something has historical significance, relevance, or impact specifically in relation to a given entity or context.
- 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_69f66e65c29481909283644a96b90eb8 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:41 p.m.