Triple
T15212258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Georgia Time |
E363543
|
entity |
| Predicate | keptYearRound |
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: [South Georgia Time, keptYearRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptYearRound Context triple: [South Georgia Time, keptYearRound, true]
-
A.
accessibleYearRound
Indicates that the subject can be accessed or used during all seasons of the year without interruption.
-
B.
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.
-
C.
keptOn
Indicates that one entity is stored, placed, or maintained on the surface or location of another entity over a period of time.
-
D.
isYearRoundCommunity
Indicates that a place or settlement is inhabited and functions as a community throughout the entire year, rather than only seasonally or temporarily.
-
E.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076c9e2481909d7a464b2172f4bf |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.