Triple
T38388544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibéria |
E899644
|
entity |
| Predicate | hasMovementTitle3 |
P172397
|
FINISHED |
| Object | Le matin d’un jour de fête |
—
|
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: Le matin d’un jour de fête | Statement: [Ibéria, hasMovementTitle3, Le matin d’un jour de fête]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementTitle3 Context triple: [Ibéria, hasMovementTitle3, Le matin d’un jour de fête]
-
A.
movementTitle3
chosen
Indicates the formal title or name given to the third movement within a larger multi-movement work.
-
B.
hasMovementWithProgrammaticTitle
Indicates that a musical work includes a movement whose title is programmatically descriptive (i.e., suggests a narrative, scene, or extra-musical idea).
-
C.
movement2Title
Indicates a relationship where a specific movement, action, or motion is associated with or labeled by a particular title or name.
-
D.
movement1Title
Indicates the title or descriptive label assigned to a specific movement within a larger work or sequence.
-
E.
haveMovementFor
Indicates that an entity exhibits or is assigned a specific type or pattern of movement in relation to another entity or context.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:31 p.m.