Triple
T2215633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Bennet (Benjamin Whitrow) |
E48024
|
entity |
| Predicate | castingType |
P36854
|
FINISHED |
| Object | supporting role |
—
|
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: supporting role | Statement: [Mr. Bennet (Benjamin Whitrow), castingType, supporting role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castingType Context triple: [Mr. Bennet (Benjamin Whitrow), castingType, supporting role]
-
A.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
-
B.
castOutOf
Indicates that one entity is expelled or forcibly removed from another entity, place, or group.
-
C.
castFrom
Indicates that one entity is transformed or converted from another, typically changing its type or representation while preserving its underlying value or identity.
-
D.
typicalCasting
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
E.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbff11574819091d1b50d637ae767 |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.