Triple
T8676530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavane pour une infante défunte |
E205928
|
entity |
| Predicate | secondVersion |
P84426
|
FINISHED |
| Object | orchestral version |
—
|
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: orchestral version | Statement: [Pavane pour une infante défunte, secondVersion, orchestral version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondVersion Context triple: [Pavane pour une infante défunte, secondVersion, orchestral version]
-
A.
secondFullVersionReference
Indicates that an entity refers to a second complete or fully detailed version of another entity.
-
B.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
C.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
D.
secondEpisode
Indicates that one episode is the immediate successor (second in order) to a preceding episode within the same series or sequence.
-
E.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:32 p.m.