Triple
T32290738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pohnpei Time |
E824958
|
entity |
| Predicate | isUsedYearRound |
P8056
|
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: [Pohnpei Time, isUsedYearRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedYearRound Context triple: [Pohnpei Time, isUsedYearRound, true]
-
A.
isUsedAllYear
chosen
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
B.
accessibleYearRound
Indicates that the subject can be accessed or used during all seasons of the year without interruption.
-
C.
hasYearRoundFlow
Indicates that the related water body or flow system maintains continuous discharge throughout the entire year without drying up seasonally.
-
D.
hasUseSeason
Indicates the season or time of year during which something is intended or suitable to be used.
-
E.
isYearRoundCommunity
Indicates that a place or settlement is inhabited and functions as a community throughout the entire year, rather than only seasonally or temporarily.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:44 a.m.