Triple
T21681570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostap Bulba |
E535119
|
entity |
| Predicate | facesDeath |
P145428
|
FINISHED |
| Object | without crying out |
—
|
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: without crying out | Statement: [Ostap Bulba, facesDeath, without crying out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesDeath Context triple: [Ostap Bulba, facesDeath, without crying out]
-
A.
featuresDeath
Indicates that the subject includes, depicts, or involves a death or deaths as a notable element.
-
B.
deathOvers
Indicates the number of overs bowled in the final phase of a limited-overs cricket innings, typically focused on the closing overs where scoring and wicket-taking intensify.
-
C.
viewOfDeath
Indicates a subject’s beliefs, attitudes, or conceptual understanding regarding death.
-
D.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
-
E.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c69990819088a1134ecea09099 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:43 p.m.