Triple
T27188215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arendelle village |
E683393
|
entity |
| Predicate | notableSeasonalDepiction |
P80360
|
FINISHED |
| Object | 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: winter | Statement: [Arendelle village, notableSeasonalDepiction, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeasonalDepiction Context triple: [Arendelle village, notableSeasonalDepiction, winter]
-
A.
depictionSeason
chosen
Indicates that one entity is a visual or representational depiction of a particular season associated with another entity.
-
B.
seasonsFeatured
Indicates that certain seasons of a series or competition are highlighted, showcased, or given special prominence in relation to an entity.
-
C.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
D.
visibleInSeason
Indicates that something can be seen or is observable during a particular season.
-
E.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: April 27, 2026, 9:31 a.m.