Triple
T22638495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Bruce |
E558750
|
entity |
| Predicate | positionInCasting |
P69300
|
FINISHED |
| Object | supporting actor |
—
|
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 actor | Statement: [David Bruce, positionInCasting, supporting actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCasting Context triple: [David Bruce, positionInCasting, supporting actor]
-
A.
positionInCast
chosen
Indicates the specific role or placement an individual holds within the cast of a production, such as their billing order or credited position.
-
B.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
C.
positionInCasteSystem
Indicates the relative social rank or standing an entity holds within a hierarchical caste system.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700f9fac8190b82190a54be22413 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.