Triple
T15422751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Village |
E369423
|
entity |
| Predicate | typicalClosingPeriod |
P105836
|
FINISHED |
| Object | mid to late 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: mid to late winter | Statement: [Winter Village, typicalClosingPeriod, mid to late winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClosingPeriod Context triple: [Winter Village, typicalClosingPeriod, mid to late winter]
-
A.
typicalClosing
Indicates that an entity represents a standard or commonly used way of ending or concluding another entity (such as a message, document, or interaction).
-
B.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
E.
typicalEndDateRange
chosen
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
- 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.