Triple
T36945505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 4 in A minor |
E913897
|
entity |
| Predicate | workChronologyNext |
P187448
|
FINISHED |
| Object | Symphony No. 5 in E-flat major |
E911282
|
NE 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: Symphony No. 5 in E-flat major | Statement: [Symphony No. 4 in A minor, workChronologyNext, Symphony No. 5 in E-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workChronologyNext Context triple: [Symphony No. 4 in A minor, workChronologyNext, Symphony No. 5 in E-flat major]
-
A.
workChronologyPosition
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
B.
workChronicles
Indicates that one entity documents, records, or narrates the work-related activities, history, or experiences of another entity.
-
C.
workChronologySubject
Indicates that the subject is the primary entity whose sequence of work-related events or positions is being chronologically described.
-
D.
chronologyPreviousWorkOf
Indicates that one work temporally precedes and is part of the earlier sequence in the overall body of another work.
-
E.
laterWorkPeriod
Indicates that one work period occurs after another in time.
- F. None of above. chosen
Provenance (5 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e16450d288190b530a1b0b67208ff |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:13 p.m.