Triple
T31207570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coriantumr |
E795642
|
entity |
| Predicate | lastManStanding |
P19817
|
FINISHED |
| Object | Jaredite nation |
—
|
NE NERFINISHED |
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: Jaredite nation | Statement: [Coriantumr, lastManStanding, Jaredite nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastManStanding Context triple: [Coriantumr, lastManStanding, Jaredite nation]
-
A.
lastStandWith
Indicates a relationship where entities join together in a final, desperate, or decisive effort or resistance, typically under extreme pressure or near-defeat conditions.
-
B.
lastRemnantOf
chosen
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
C.
saidToBeTheLast
Indicates that something or someone is claimed or reported to be the final instance or member in a sequence, series, or group.
-
D.
lastMP
Indicates that one entity is the most recent Member of Parliament (MP) associated with, representing, or holding office for the other entity.
-
E.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c24de048190973b05290ff5c404 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.