Triple
T32362417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymonda, Op. 57 |
E826898
|
entity |
| Predicate | hasSuiteArrangements |
P138750
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Raymonda, Op. 57, hasSuiteArrangements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuiteArrangements Context triple: [Raymonda, Op. 57, hasSuiteArrangements, yes]
-
A.
hasArrangement
Indicates that one entity possesses, follows, or is organized according to a particular configuration, setup, or ordering defined by another entity.
-
B.
hasArrangementFeature
Indicates that one entity possesses a specific structural or spatial arrangement characteristic related to another entity or context.
-
C.
hasArrangementFor
Indicates that one entity has an established plan, setup, or provision in place to accommodate, support, or serve another entity or purpose.
-
D.
hasLaterArrangements
Indicates that there exist subsequent plans, agreements, or arrangements that occur after or supersede earlier ones.
-
E.
hasArrangementBy
chosen
Indicates that something (such as a work or piece) is in an arranged form created by a particular arranger.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 12:49 a.m.