Triple
T11010529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierce Hawthorne |
E260233
|
entity |
| Predicate | causeOfExitFromSeries |
P11350
|
FINISHED |
| Object | death (off-screen) |
—
|
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: death (off-screen) | Statement: [Pierce Hawthorne, causeOfExitFromSeries, death (off-screen)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfExitFromSeries Context triple: [Pierce Hawthorne, causeOfExitFromSeries, death (off-screen)]
-
A.
departureFromSeries
Indicates that an entity stops being part of, or exits from, a particular series or sequence.
-
B.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
C.
endOfSeriesStatus
Indicates that a series, sequence, or collection has reached its final state or completion status.
-
D.
end cause
Indicates that one event or action brings about the termination or cessation of another event, state, or process.
-
E.
seriesRunEnd
Indicates the point or event at which a series, sequence, or recurring run of something concludes.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797899a388190aa8fe813eac4dba7 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.