Triple
T16584380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abigail Marston |
E402914
|
entity |
| Predicate | statusInRedDeadRedemption2 |
P123401
|
FINISHED |
| Object | alive |
—
|
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: alive | Statement: [Abigail Marston, statusInRedDeadRedemption2, alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRedDeadRedemption2 Context triple: [Abigail Marston, statusInRedDeadRedemption2, alive]
-
A.
statusInDiabloII
Indicates the role, condition, or classification an entity holds within the context of the game Diablo II.
-
B.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
E.
FrontierStatus
Indicates the status or condition of something in relation to a boundary, edge, or frontier context (such as being at, beyond, or within that frontier).
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35999f80c8190852fd4137bc45a80 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.