Triple
T30741284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coriantumr |
E782694
|
entity |
| Predicate | soleSurvivorOf |
P2544
|
FINISHED |
| Object | final Jaredite war |
—
|
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 Jaredite war | Statement: [Coriantumr, soleSurvivorOf, final Jaredite war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soleSurvivorOf Context triple: [Coriantumr, soleSurvivorOf, final Jaredite war]
-
A.
survivorWith
Indicates a relationship where one entity survives an event or condition together with, or in the presence of, another entity.
-
B.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
C.
survivorOfAttack
Indicates that one entity has lived through and remains alive after being subjected to an attack carried out by another entity.
-
D.
survivorTerm
chosen
Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
-
E.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f68da34819092a2e476e5f6ee05 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.