Triple
T30978084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Baumgartner |
E789284
|
entity |
| Predicate | character role |
P155206
|
FINISHED |
| Object | Kevin Malone |
—
|
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: Kevin Malone | Statement: [Brian Baumgartner, character role, Kevin Malone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: character role Context triple: [Brian Baumgartner, character role, Kevin Malone]
-
A.
characterPersona
chosen
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by another entity.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
characterSetting
Indicates that a character is associated with, appears in, or is situated within a particular setting or environment.
-
E.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 29, 2026, 8:55 p.m.