Triple
T21426596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonia |
E528572
|
entity |
| Predicate | movementAddedLater |
P4097
|
FINISHED |
| Object | fifth movement |
—
|
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: fifth movement | Statement: [Sinfonia, movementAddedLater, fifth movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementAddedLater Context triple: [Sinfonia, movementAddedLater, fifth movement]
-
A.
laterAdditionsBy
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
E.
laterDiscovered
Indicates that one entity was discovered or found at a time subsequent to the discovery 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813c7a048190a400e364c8df1dcf |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:49 p.m.