Triple
T35046094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legend of Duluoz |
E1011198
|
entity |
| Predicate | protagonistAliasOf |
P46224
|
FINISHED |
| Object | Jack Kerouac |
—
|
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: Jack Kerouac | Statement: [Legend of Duluoz, protagonistAliasOf, Jack Kerouac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistAliasOf Context triple: [Legend of Duluoz, protagonistAliasOf, Jack Kerouac]
-
A.
protagonistAlsoKnownAs
chosen
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
B.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
C.
protagonistRealWorldName
Indicates that a character’s name in the real world (outside a fictional, virtual, or alternate setting) is associated with that character as the story’s protagonist.
-
D.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
E.
protagonistFullName
Indicates that the subject entity is the full, proper name (including given and family names) of 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.