Triple
T37039144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 7 in C major |
E916730
|
entity |
| Predicate | laterRevision |
P42870
|
FINISHED |
| Object | single-movement symphony |
—
|
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: single-movement symphony | Statement: [Symphony No. 7 in C major, laterRevision, single-movement symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRevision Context triple: [Symphony No. 7 in C major, laterRevision, single-movement symphony]
-
A.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
B.
laterAgeRevision
Indicates that one entity represents a revised age that is later (or updated to a more advanced point in time) than the age specified by another entity.
-
C.
laterModification
chosen
Indicates that one entity is a modification or revision that occurs after another in time.
-
D.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
E.
laterRevertedTo
Indicates that a prior change, state, or condition was subsequently undone, returning the subject to its earlier form or status.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:14 p.m.