Triple
T30614717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiwetel Ejiofor as Solomon Northup |
E779282
|
entity |
| Predicate | characterStatusDuringPlot |
P52203
|
FINISHED |
| Object | enslaved man |
—
|
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: enslaved man | Statement: [Chiwetel Ejiofor as Solomon Northup, characterStatusDuringPlot, enslaved man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterStatusDuringPlot Context triple: [Chiwetel Ejiofor as Solomon Northup, characterStatusDuringPlot, enslaved man]
-
A.
characterStatusInStory
chosen
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
B.
plotCharacter
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
C.
characterReveals
Indicates that one character discloses or makes known information, feelings, or intentions to another character.
-
D.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
E.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:26 p.m.