Triple
T2744697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamashita v. Styer |
E60837
|
entity |
| Predicate | sentenceUpheld |
P3106
|
FINISHED |
| Object | death |
—
|
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 | Statement: [Yamashita v. Styer, sentenceUpheld, death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentenceUpheld Context triple: [Yamashita v. Styer, sentenceUpheld, death]
-
A.
upheldBy
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
B.
affirms
chosen
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
C.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
D.
receivedSentence
Indicates that one entity has been given or accepted a sentence (such as a legal punishment or formal judgment) from another entity or authority.
-
E.
sentenceOf
Indicates that one entity is a sentence that belongs to, is contained in, or is part of another larger text or document.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb32ef74819096ae399d16d4f31d |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.