Triple
T29842771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forlane (Ravel) |
E757845
|
entity |
| Predicate | orchestrationByComposer |
P105966
|
FINISHED |
| Object | Maurice Ravel |
—
|
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: Maurice Ravel | Statement: [Forlane (Ravel), orchestrationByComposer, Maurice Ravel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestrationByComposer Context triple: [Forlane (Ravel), orchestrationByComposer, Maurice Ravel]
-
A.
musicOrchestratedBy
chosen
Indicates that a piece of music or musical work is arranged or orchestrated by a specific person or entity.
-
B.
isOrchestralWorkBy
Indicates that a particular orchestral work was created or composed by a specified composer or artist.
-
C.
orchestrationIncludes
Indicates that one orchestration contains, incorporates, or makes use of another orchestration as part of its overall structure or process.
-
D.
orchestrationFor
Indicates a relationship where one entity coordinates, arranges, or manages the actions or interactions of another entity or set of entities to achieve a desired outcome.
-
E.
orchestration
Indicates the coordination and arrangement of multiple components or processes to work together harmoniously toward a unified outcome.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760b3d6081909d0e3748483989a4 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:40 p.m.