Triple
T30798896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bent (stage production) |
E784310
|
entity |
| Predicate | notableOriginalLondonLeadActor |
P201142
|
FINISHED |
| Object | Ian McKellen |
E46699
|
NE 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: Ian McKellen | Statement: [Bent (stage production), notableOriginalLondonLeadActor, Ian McKellen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOriginalLondonLeadActor Context triple: [Bent (stage production), notableOriginalLondonLeadActor, Ian McKellen]
-
A.
notableWestEndPortrayalBy
Indicates that a person is recognized for a significant or distinguished acting role in London’s West End associated with the subject.
-
B.
notableStarName
Indicates that the subject is known by the specified star name as a notable or prominent designation.
-
C.
originallyCastLeadActor
chosen
Indicates that a person was the lead actor in the original casting of a production (before any later replacements or recasting).
-
D.
notableBearActor
Indicates that the subject is a bear who is recognized for acting roles or performances.
-
E.
notableActorInStageProduction
Indicates that a person is a distinguished or prominent actor in a particular stage production.
- F. None of above.
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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28b0b19c148190b0a248e5a0a576fe |
completed | June 10, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:42 p.m.