Triple
T34094961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estancia |
E874399
|
entity |
| Predicate | originalScoreForm |
P199653
|
FINISHED |
| Object | ballet suite for orchestra |
—
|
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: ballet suite for orchestra | Statement: [Estancia, originalScoreForm, ballet suite for orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalScoreForm Context triple: [Estancia, originalScoreForm, ballet suite for orchestra]
-
A.
originalForm
Indicates that one entity is the earlier, source, or initial version from which another entity is derived or transformed.
-
B.
featuresOriginalScore
Indicates that an entity includes or is accompanied by its initial, unaltered score or musical composition.
-
C.
originalRating
Indicates the initial or baseline rating assigned to something before any updates, changes, or adjustments are made.
-
D.
originallyForm
Indicates that an entity existed in a particular initial shape, structure, or configuration before undergoing change or transformation.
-
E.
hasOriginalScoreFor
chosen
Indicates that one entity is the original musical score specifically composed for another entity, such as a film, show, or performance.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.