Triple
T14800636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walk of atonement of Cersei Lannister |
E347900
|
entity |
| Predicate | typeOfPenance |
P38261
|
FINISHED |
| Object | walk of atonement |
—
|
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: walk of atonement | Statement: [Walk of atonement of Cersei Lannister, typeOfPenance, walk of atonement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPenance Context triple: [Walk of atonement of Cersei Lannister, typeOfPenance, walk of atonement]
-
A.
performedPenanceAt
Indicates that an entity carried out an act of penance at a specific place or location.
-
B.
contritionType
chosen
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
C.
punishmentMethod
Indicates the method or means by which a punishment is carried out on an entity.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
aimOfPunishment
Indicates that a specified purpose or objective is the intended goal or rationale behind a particular act of punishment.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.