Triple
T34847826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poker Flat |
E1004518
|
entity |
| Predicate | banishesCharacter |
P181920
|
FINISHED |
| Object | John Oakhurst |
—
|
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: John Oakhurst | Statement: [Poker Flat, banishesCharacter, John Oakhurst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: banishesCharacter Context triple: [Poker Flat, banishesCharacter, John Oakhurst]
-
A.
dismissesCharacter
Indicates that one character rejects, disbelieves, or disregards another character, often minimizing their importance, ideas, or concerns.
-
B.
removedCharacter
Indicates that a character was taken out or deleted from a text, sequence, or collection.
-
C.
revivesCharacterFrom
Indicates that one entity brings another previously dead or inactive character back to life or active status.
-
D.
lostByCharacter
Indicates that something (such as a game, contest, or opportunity) was lost by the specified character.
-
E.
exorcisedBy
Indicates that an entity has had a spirit, demon, or malign supernatural influence driven out or removed by another entity.
- F. None of above. chosen
Provenance (4 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.