Triple
T23594064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silent Night |
E582565
|
entity |
| Predicate | wasFirstPerformedInPlace |
P152845
|
FINISHED |
| Object | Oberndorf bei Salzburg |
—
|
NE NERFINISHED |
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: Oberndorf bei Salzburg | Statement: [Silent Night, wasFirstPerformedInPlace, Oberndorf bei Salzburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstPerformedInPlace Context triple: [Silent Night, wasFirstPerformedInPlace, Oberndorf bei Salzburg]
-
A.
performedFirst
Indicates that one entity carried out an action or event before another entity did.
-
B.
firstPerformedAs
Indicates the initial occasion or context in which an entity (such as a work, role, or piece) was performed by a particular performer or group.
-
C.
firstPerformedWith
Indicates that an action or work was initially performed in conjunction with a specified collaborator, group, or medium.
-
D.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
-
E.
wasFirstOf
Indicates that the subject is the earliest or initial instance in a series, sequence, or group of similar entities or events.
- F. None of above. chosen
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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:42 p.m.