Triple
T2577231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 14 in C-sharp minor, Op. 27 No. 2 "Moonlight" |
E57004
|
entity |
| Predicate | set |
P40357
|
FINISHED |
| Object | Op. 27 |
—
|
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: Op. 27 | Statement: [Piano Sonata No. 14 in C-sharp minor, Op. 27 No. 2 "Moonlight", set, Op. 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: set Context triple: [Piano Sonata No. 14 in C-sharp minor, Op. 27 No. 2 "Moonlight", set, Op. 27]
-
A.
sets
Indicates that an entity places, positions, or puts another entity into a particular state, location, or configuration.
-
B.
setsOut
Indicates that an entity begins a journey, course of action, or process, moving from an initial state or location toward a goal or destination.
-
C.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
sharesSetsWith
Indicates that two entities have one or more sets in common, or participate in at least one identical set.
-
E.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd209d934819093600889af9104c3 |
completed | March 7, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:49 p.m.