Triple
T17700648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJT |
E441288
|
entity |
| Predicate | offsetDoesNotChangeSeasonally |
P13686
|
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: [TJT, offsetDoesNotChangeSeasonally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetDoesNotChangeSeasonally Context triple: [TJT, offsetDoesNotChangeSeasonally, true]
-
A.
hasNoSeasonalClockChanges
chosen
Indicates that a place or system does not adjust its clocks for seasonal time changes such as daylight saving time.
-
B.
hasSeasonalPositionSouthernHemisphere
Indicates that an entity’s seasonal position or phase is defined specifically with respect to conditions in the Southern Hemisphere.
-
C.
hasOppositeSeasonTime
Indicates that two locations experience opposite seasons at the same time of year (e.g., when it is summer in one, it is winter in the other).
-
D.
doesNotObserveDaylightSavingTimeIn
Indicates that a place or jurisdiction does not adjust its clocks for daylight saving time in the specified region or context.
-
E.
hasSeasonalMigration
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4715ae1fc81908438a1bba970c6ec |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:04 a.m.