Triple
T29576294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Um Mitternacht |
E753451
|
entity |
| Predicate | laterArrangementFor |
P197321
|
FINISHED |
| Object | voice and orchestra |
—
|
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: voice and orchestra | Statement: [Um Mitternacht, laterArrangementFor, voice and orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterArrangementFor Context triple: [Um Mitternacht, laterArrangementFor, voice and orchestra]
-
A.
laterArrangementBy
Indicates that one arrangement or configuration occurs after or succeeds another in time.
-
B.
laterReception
Indicates that one entity receives or accepts something at a time that is later than when another related reception or event occurs.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
E.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: April 28, 2026, 6:03 p.m.