Triple
T25570772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic tundra |
E640966
|
entity |
| Predicate | daylightPattern |
P63429
|
FINISHED |
| Object | polar night in winter |
—
|
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: polar night in winter | Statement: [Arctic tundra, daylightPattern, polar night in winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightPattern Context triple: [Arctic tundra, daylightPattern, polar night in winter]
-
A.
dayPattern
chosen
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
B.
governsDaylightPatternFor
Indicates that one entity determines or regulates the pattern, timing, or distribution of daylight experienced by another entity.
-
C.
daylightEffect
Indicates the influence or change that daylight has on a given entity, condition, or process.
-
D.
daylightSavingRule
Indicates the rule or policy that defines when and how daylight saving time is applied or adjusted for a given context.
-
E.
dayNightVariant
Indicates a relationship where one entity is a day-time version and the other is a night-time version of the same underlying thing.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8ffb11c8190add0643923c6eaf8 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:57 p.m.