Triple
T35334950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludgerusdom in Billerbeck |
E1020425
|
entity |
| Predicate | hasProcessionsOn |
P89638
|
FINISHED |
| Object | Feast of Saint Ludger |
E2136944
|
NE 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: Feast of Saint Ludger | Statement: [Ludgerusdom in Billerbeck, hasProcessionsOn, Feast of Saint Ludger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessionsOn Context triple: [Ludgerusdom in Billerbeck, hasProcessionsOn, Feast of Saint Ludger]
-
A.
hasProcessionDuring
Indicates that a procession or ceremonial march takes place during a specified time period or event.
-
B.
hasProcessionFrom
Indicates that a procession, ceremony, or formal movement originates from or starts at a specified source location or entity.
-
C.
organizesProcessions
Indicates that an entity is responsible for planning, coordinating, and managing the execution of processions or parades.
-
D.
mainProcessionDay
chosen
Indicates the specific day on which the primary or central procession of an event or celebration takes place.
-
E.
locationOfProcessions
Indicates the place where processions occur or are held.
- F. None of above.
Provenance (4 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cacd14081909eb4498044d91235 |
completed | June 21, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.