Triple
T1297575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertie Wooster |
E27687
|
entity |
| Predicate | oftenNarrates |
P11859
|
FINISHED |
| Object | Jeeves stories |
—
|
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: Jeeves stories | Statement: [Bertie Wooster, oftenNarrates, Jeeves stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenNarrates Context triple: [Bertie Wooster, oftenNarrates, Jeeves stories]
-
A.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
B.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
C.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
-
D.
hasNarrative
chosen
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
E.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.