Triple
T23809976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCarthy |
E589825
|
entity |
| Predicate | roleOfLaetitiaSadier |
P153644
|
FINISHED |
| Object | backing vocalist |
—
|
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: backing vocalist | Statement: [McCarthy, roleOfLaetitiaSadier, backing vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfLaetitiaSadier Context triple: [McCarthy, roleOfLaetitiaSadier, backing vocalist]
-
A.
roleOfIrèneJacob
Indicates that an entity holds the role or character portrayed by Irène Jacob in a work or context.
-
B.
roleOfCarmen Pavlovic
Indicates that the specified role or position is held or performed by Carmen Pavlovic.
-
C.
roleOfPeter Seligmann
Indicates that the specified role or position is held by Peter Seligmann.
-
D.
Perlmutter
Indicates a relationship or action associated with the name "Perlmutter," such as authorship, attribution, or involvement, depending on the specific ontology or dataset in which it appears.
-
E.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7549c44819099b9e7eb36747f38 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:57 p.m.