Triple
T3989133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Praxis |
E86943
|
entity |
| Predicate | characterStatus |
P52203
|
FINISHED |
| Object | deceased by end of Jak II |
—
|
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 by end of Jak II | Statement: [Baron Praxis, characterStatus, deceased by end of Jak II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterStatus Context triple: [Baron Praxis, characterStatus, deceased by end of Jak II]
-
A.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
B.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
C.
characterStatusInStory
chosen
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
D.
characterDescription
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
E.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.