Triple
T23730021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Factotum |
E586385
|
entity |
| Predicate | protagonistIsAlterEgoOf |
P86336
|
FINISHED |
| Object | Charles Bukowski |
—
|
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: Charles Bukowski | Statement: [Factotum, protagonistIsAlterEgoOf, Charles Bukowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistIsAlterEgoOf Context triple: [Factotum, protagonistIsAlterEgoOf, Charles Bukowski]
-
A.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
B.
hasFictionalAlterEgoOf
chosen
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
C.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
hasAlterEgoCostume
Indicates that an entity has a distinct costume specifically associated with its alter ego identity.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9180bf48190a6c3656ef0530463 |
completed | April 29, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.