Triple
T15422750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Village |
E369423
|
entity |
| Predicate | typicalOpeningPeriod |
P84192
|
FINISHED |
| Object | late fall to early 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: late fall to early winter | Statement: [Winter Village, typicalOpeningPeriod, late fall to early winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOpeningPeriod Context triple: [Winter Village, typicalOpeningPeriod, late fall to early winter]
-
A.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
seasonOpeningOrClosing
Indicates that an event marks either the beginning or the end of a particular season.
-
C.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
D.
typicallyOpenFromMonth
Indicates the month from which something (such as a place, service, or facility) is usually open or begins operating.
-
E.
typicalStartTimeOfYear
Indicates the usual or characteristic time of year when something typically begins or occurs.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.