Triple
T9404442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death of Boris |
E226549
|
entity |
| Predicate | hasActPosition |
P88992
|
FINISHED |
| Object | final scene |
—
|
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: final scene | Statement: [Death of Boris, hasActPosition, final scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActPosition Context triple: [Death of Boris, hasActPosition, final scene]
-
A.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
B.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
C.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
hasAssociatedPosition
Indicates that one entity is linked to a specific role, job, or spatial/organizational position associated with it.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:46 p.m.