Triple
T11179607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vierzehn Nothelfer |
E264501
|
entity |
| Predicate | collectiveFeastType |
P9865
|
FINISHED |
| Object | local feast day |
—
|
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: local feast day | Statement: [Vierzehn Nothelfer, collectiveFeastType, local feast day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveFeastType Context triple: [Vierzehn Nothelfer, collectiveFeastType, local feast day]
-
A.
feastType
chosen
Indicates the specific kind or category of feast associated with an event or occasion.
-
B.
feastTraditionalName
Indicates the traditional or customary name by which a particular feast or celebration is known.
-
C.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
D.
extendedFeast
Indicates a situation where a feast or celebratory meal continues for an unusually long or prolonged period of time.
-
E.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e899c6288190b39e090fa9cdc883 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.