Triple
T15425606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Frey |
E369500
|
entity |
| Predicate | honorCustom |
P118736
|
FINISHED |
| Object | guest right (violated at the Red Wedding) |
—
|
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: guest right (violated at the Red Wedding) | Statement: [House Frey, honorCustom, guest right (violated at the Red Wedding)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorCustom Context triple: [House Frey, honorCustom, guest right (violated at the Red Wedding)]
-
A.
honorStyle
Indicates the manner or level of respect, formality, or honor expressed toward or between entities.
-
B.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
C.
hasHolidayCustom
Indicates that there is a specific traditional practice or custom associated with a particular holiday.
-
D.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
E.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
- F. None of above. chosen
Provenance (4 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec1fb288190a3625b8e4f487dd1 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:20 a.m.