Triple
T37536729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krampuslauf |
E933218
|
entity |
| Predicate | typicallyHeldOnOrAround |
P39845
|
FINISHED |
| Object | 5 December |
—
|
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: 5 December | Statement: [Krampuslauf, typicallyHeldOnOrAround, 5 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyHeldOnOrAround Context triple: [Krampuslauf, typicallyHeldOnOrAround, 5 December]
-
A.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
-
B.
oftenHeldDuring
Indicates that one event or state commonly occurs at the same time as, or within the temporal span of, another event or period.
-
C.
occursOnOrAround
chosen
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
-
D.
festivalHeldOnOrAround
Indicates that a festival customarily takes place on or near a specified date or time period.
-
E.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.