Triple
T11755560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voices of Spring |
E279513
|
entity |
| Predicate | isArrangedAs |
P46740
|
FINISHED |
| Object | piano solo |
—
|
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: piano solo | Statement: [Voices of Spring, isArrangedAs, piano solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArrangedAs Context triple: [Voices of Spring, isArrangedAs, piano solo]
-
A.
isArrangementOf
chosen
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
B.
arrangementType
Indicates the specific kind or category of arrangement that characterizes how the related entities are organized or structured in relation to each other.
-
C.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
-
D.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
E.
hasArrangementFor
Indicates that one entity has an established plan, setup, or provision in place to accommodate, support, or serve another entity or purpose.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50c8d708190ad79ecb57b715d04 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.