Triple
T9778104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard II (stage performances) |
E237295
|
entity |
| Predicate | casting |
P18965
|
FINISHED |
| Object | star vehicle for Ian McKellen |
—
|
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: star vehicle for Ian McKellen | Statement: [Richard II (stage performances), casting, star vehicle for Ian McKellen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casting Context triple: [Richard II (stage performances), casting, star vehicle for Ian McKellen]
-
A.
cast
chosen
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
B.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
-
C.
castingChoiceFor
Indicates a relationship where a particular casting decision or option is selected or designated for a specific role, production, or performance.
-
D.
castType
Indicates the specific kind or category of casting relationship that exists between two entities.
-
E.
castingType
Indicates the specific method or category of casting used to transform or represent one entity in terms of another.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13545808190a47544b0cc666e20 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:26 p.m.