Triple
T9457948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Adagio |
E228064
|
entity |
| Predicate | traditionallyPerformedBy |
P32287
|
FINISHED |
| Object | principal ballerina |
—
|
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: principal ballerina | Statement: [Rose Adagio, traditionallyPerformedBy, principal ballerina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPerformedBy Context triple: [Rose Adagio, traditionallyPerformedBy, principal ballerina]
-
A.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
B.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
C.
traditionalPerformer
Indicates that an entity performs or practices traditional, culturally inherited arts, rituals, or performances.
-
D.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
E.
performedFrom
Indicates that an action or operation is carried out starting at or originating from a specified source location, context, or entity.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.