Triple
T985173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyle Reese |
E21261
|
entity |
| Predicate | statusInTheTerminator |
P127
|
FINISHED |
| Object | deceased |
—
|
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: deceased | Statement: [Kyle Reese, statusInTheTerminator, deceased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTheTerminator Context triple: [Kyle Reese, statusInTheTerminator, deceased]
-
A.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
-
D.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4959fe48190a78bd811cbc888ab |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.