Triple
T14957160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa's elves |
E372960
|
entity |
| Predicate | seasonalActivityPeak |
P70162
|
FINISHED |
| Object | weeks before Christmas |
—
|
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: weeks before Christmas | Statement: [Santa's elves, seasonalActivityPeak, weeks before Christmas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalActivityPeak Context triple: [Santa's elves, seasonalActivityPeak, weeks before Christmas]
-
A.
activityPeakPeriod
chosen
Indicates the time period during which an activity reaches its highest level or intensity.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
seasonalActivitiesAtTop
Indicates that certain activities occur or are available at the top of a location (such as a hill, building, or structure) only during specific seasons.
-
D.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
E.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6cc73848190ac181782b20dc838 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:40 a.m.