Triple
T6397763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pli selon pli |
E143981
|
entity |
| Predicate | centralPerformerRole |
P24740
|
FINISHED |
| Object | soprano 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: soprano soloist | Statement: [Pli selon pli, centralPerformerRole, soprano soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPerformerRole Context triple: [Pli selon pli, centralPerformerRole, soprano soloist]
-
A.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
-
B.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
C.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
D.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
E.
talentShowRole
Indicates the specific function or position an entity holds within the context of a talent show (e.g., performer, judge, host).
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06896d180819091548a728e903184 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.