Triple
T7874630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hostages Trial |
E182819
|
entity |
| Predicate | sentencesIncluded |
P79502
|
FINISHED |
| Object | death sentences |
—
|
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 sentences | Statement: [Hostages Trial, sentencesIncluded, death sentences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentencesIncluded Context triple: [Hostages Trial, sentencesIncluded, death sentences]
-
A.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
-
B.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
includesSaying
Indicates that one entity (such as a text, speech, or communication) contains or incorporates a particular saying, phrase, or quoted expression.
-
D.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a961188190b2f12f8fe5d66641 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:56 p.m.