Triple
T23754585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 4 |
E587068
|
entity |
| Predicate | successorInCycle |
P153563
|
FINISHED |
| Object | Mahler Symphony No. 5 |
—
|
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: Mahler Symphony No. 5 | Statement: [Mahler Symphony No. 4, successorInCycle, Mahler Symphony No. 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInCycle Context triple: [Mahler Symphony No. 4, successorInCycle, Mahler Symphony No. 5]
-
A.
successorIndex
Indicates the position or identifier that directly follows a given index in an ordered sequence.
-
B.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
-
C.
successorInPolicy
Indicates that one policy directly follows and replaces another in a sequence or hierarchy of policies.
-
D.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
E.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc561b081908bfd516ef5e2dcfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:13 p.m.