Triple
T28135749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Confession of Joe Cullen |
E714198
|
entity |
| Predicate | titleCharacterRole |
P92378
|
FINISHED |
| Object | accused 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: accused man | Statement: [The Confession of Joe Cullen, titleCharacterRole, accused man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterRole Context triple: [The Confession of Joe Cullen, titleCharacterRole, accused man]
-
A.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
B.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
C.
titleCharacterRelation
chosen
Indicates the relationship between a work’s title and a specific character it references or centers on.
-
D.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
E.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 9:49 p.m.