Triple
T1836760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 "Kaddish" |
E41083
|
entity |
| Predicate | revisedVersion |
P4421
|
FINISHED |
| Object | 1977 revision |
—
|
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: 1977 revision | Statement: [Symphony No. 3 "Kaddish", revisedVersion, 1977 revision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedVersion Context triple: [Symphony No. 3 "Kaddish", revisedVersion, 1977 revision]
-
A.
updated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
reformulatedConcept
Indicates that one concept is a revised, rephrased, or otherwise modified version of another concept while preserving its core meaning.
-
C.
reorganized
Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
-
D.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
E.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.