Triple
T3010994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winterfest light displays |
E82217
|
entity |
| Predicate | operatesDuringSeason |
P33199
|
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: [Winterfest light displays, operatesDuringSeason, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDuringSeason Context triple: [Winterfest light displays, operatesDuringSeason, winter]
-
A.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
B.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
C.
visibleInSeason
chosen
Indicates that something can be seen or is observable during a particular season.
-
D.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4e2c8c8190a8fed3604780826b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.