Triple
T20360405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charmian |
E496758
|
entity |
| Predicate | loyalToDeath |
P1201
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Charmian, loyalToDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyalToDeath Context triple: [Charmian, loyalToDeath, true]
-
A.
diesInArmsOf
Indicates that one entity dies while being physically held or embraced by another entity.
-
B.
diedFor
Indicates that one entity’s death occurred as a sacrifice or in order to benefit, save, or serve another entity.
-
C.
allegiance
chosen
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, another entity.
-
E.
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.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678584294819093788ccf2fb8e588 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.