Triple
T38010360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Blackpool |
E948346
|
entity |
| Predicate | isFiredBy |
P88603
|
FINISHED |
| Object | Josiah Bounderby |
—
|
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: Josiah Bounderby | Statement: [Stephen Blackpool, isFiredBy, Josiah Bounderby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiredBy Context triple: [Stephen Blackpool, isFiredBy, Josiah Bounderby]
-
A.
firedBy
chosen
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
B.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
C.
testFiredBy
Indicates that a test or examination is initiated, triggered, or executed by a particular agent or system.
-
D.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
E.
firedFrom
Indicates that an entity has been dismissed or terminated from a position, job, or role by another entity.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.