Triple
T25387809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sun, Whose Rays Are All Ablaze |
E631571
|
entity |
| Predicate | commonArrangement |
P167712
|
FINISHED |
| Object | voice and piano |
—
|
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: voice and piano | Statement: [The Sun, Whose Rays Are All Ablaze, commonArrangement, voice and piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonArrangement Context triple: [The Sun, Whose Rays Are All Ablaze, commonArrangement, voice and piano]
-
A.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
B.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
C.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
-
D.
frequentlyArrangedFor
Indicates that one entity regularly organizes, schedules, or sets up something on behalf of another entity.
-
E.
isArrangementOf
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
- F. None of above. chosen
Provenance (4 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 21, 2026, 1:47 p.m.