Triple
T38598870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohe Messe in h-Moll |
E934155
|
entity |
| Predicate | firstCompletePerformanceDate |
P94859
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Hohe Messe in h-Moll, firstCompletePerformanceDate, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCompletePerformanceDate Context triple: [Hohe Messe in h-Moll, firstCompletePerformanceDate, 19th century]
-
A.
dateOfFirstPerformance
Indicates the date on which a work, such as a play or musical composition, was first publicly performed.
-
B.
lastPerformanceDate
Indicates the date on which an entity most recently carried out a performance or event.
-
C.
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.
-
D.
firstPerformedDuring
chosen
Indicates that an action, event, or performance occurred for the first time within a specified time period or during a particular event.
-
E.
firstUSPerformanceDate
Indicates the date on which something was first performed in the United States.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.