Triple
T11758949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson family murders |
E279602
|
entity |
| Predicate | hasAppealStatus |
P18643
|
FINISHED |
| Object | conviction upheld on appeal |
—
|
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: conviction upheld on appeal | Statement: [Hudson family murders, hasAppealStatus, conviction upheld on appeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAppealStatus Context triple: [Hudson family murders, hasAppealStatus, conviction upheld on appeal]
-
A.
appealStatus
chosen
Indicates the current state or outcome of an appeal within a review or decision process.
-
B.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
C.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
D.
hasDisputedStatusWith
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
-
E.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.