Triple
T31104338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Atreides |
E792754
|
entity |
| Predicate | hasAncestralMotto |
P20052
|
FINISHED |
| Object | “Never to forgive, never to forget” |
—
|
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: “Never to forgive, never to forget” | Statement: [House Atreides, hasAncestralMotto, “Never to forgive, never to forget”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralMotto Context triple: [House Atreides, hasAncestralMotto, “Never to forgive, never to forget”]
-
A.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
B.
isTraditionalMottoOf
Indicates that a phrase or saying serves as the historically established or customary motto associated with a particular entity.
-
C.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
D.
isMottoOf
chosen
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
E.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 9:03 p.m.