Triple
T16856265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto |
E409791
|
entity |
| Predicate | requiresPerformerRole |
P6843
|
FINISHED |
| Object | piano soloist |
—
|
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 soloist | Statement: [Piano Concerto, requiresPerformerRole, piano soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPerformerRole Context triple: [Piano Concerto, requiresPerformerRole, piano soloist]
-
A.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
B.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
-
C.
requiresRole
chosen
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
-
D.
requiresMember
Indicates that one entity depends on or mandates the participation, presence, or inclusion of another entity as a member in order for a condition, action, or relationship to hold.
-
E.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37d69a08190af18b421066f44f1 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.