Triple
T33324441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried & Roy |
E853226
|
entity |
| Predicate | performingPartnerOf |
P41744
|
FINISHED |
| Object | Siegfried Fischbacher |
—
|
NE NERFINISHED |
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: Siegfried Fischbacher | Statement: [Siegfried & Roy, performingPartnerOf, Siegfried Fischbacher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performingPartnerOf Context triple: [Siegfried & Roy, performingPartnerOf, Siegfried Fischbacher]
-
A.
performingPartner
chosen
Indicates that one entity is the partner who participates in or carries out a performance together with another entity.
-
B.
partnerOfArtist
Indicates a relationship where one entity is the romantic or life partner of an artist.
-
C.
partnerInQuartetWith
Indicates that two entities are members of the same quartet and are partners within that four-member group.
-
D.
partnerInMusicDuoWith
Indicates that two entities are members of the same musical duo, performing together as a two-person act.
-
E.
partnerInMusicGroupWith
Indicates that two entities are members of the same music group or band, sharing a collaborative musical partnership.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 1, 2026, 1:33 a.m.