Triple
T36945504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 in A minor |
E913897
|
entity |
| Predicate | workChronologyPrevious |
P22762
|
FINISHED |
| Object | Symphony No. 3 in C major |
—
|
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: Symphony No. 3 in C major | Statement: [Symphony No. 4 in A minor, workChronologyPrevious, Symphony No. 3 in C major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workChronologyPrevious Context triple: [Symphony No. 4 in A minor, workChronologyPrevious, Symphony No. 3 in C major]
-
A.
chronologyPreviousWorkOf
Indicates that one work temporally precedes and is part of the earlier sequence in the overall body of another work.
-
B.
chronologyPreviousYear
Indicates that one time-related entity occurs exactly one calendar year before another in a chronological sequence.
-
C.
chronologyPrevious
chosen
Indicates that one event, item, or state occurs directly before another in a chronological sequence.
-
D.
previousPeriod
Indicates that one time period directly precedes another in a sequence of periods.
-
E.
workChronicles
Indicates that one entity documents, records, or narrates the work-related activities, history, or experiences of another entity.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.