Triple
T25291038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Man Jeeves |
E634081
|
entity |
| Predicate | hasBumblingProtagonist |
P135229
|
FINISHED |
| Object | Bertie Wooster |
—
|
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: Bertie Wooster | Statement: [My Man Jeeves, hasBumblingProtagonist, Bertie Wooster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBumblingProtagonist Context triple: [My Man Jeeves, hasBumblingProtagonist, Bertie Wooster]
-
A.
hasIneptProtagonist
chosen
Indicates that the central character in a narrative is notably incompetent, unskilled, or ineffective in their role or actions.
-
B.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
-
C.
hasMisadventures
Indicates that an entity experiences or is involved in a series of troublesome, chaotic, or comically unfortunate events.
-
D.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcc8fe88190bf330715354553f6 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:22 p.m.