Triple
T26900458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of McAdenville |
E678012
|
entity |
| Predicate | hasHolidaySeason |
P66906
|
FINISHED |
| Object | Christmas season |
—
|
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: Christmas season | Statement: [Town of McAdenville, hasHolidaySeason, Christmas season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolidaySeason Context triple: [Town of McAdenville, hasHolidaySeason, Christmas season]
-
A.
hasHolidaySales
Indicates that an entity conducts or experiences sales or promotional events specifically associated with holidays.
-
B.
typicalHolidaySeasonOutput
Indicates the usual or expected level of output or activity that occurs during the holiday season.
-
C.
hasHolidayAnalog
Indicates that one entity has a corresponding or comparable counterpart in the context of a holiday or holiday-related tradition.
-
D.
hasFestivalPeriod
chosen
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
E.
hasPostFestivePeriod
Indicates that an entity experiences or is associated with a specific period of time following a festive or holiday event.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 5:50 a.m.