Triple
T31103712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mentats |
E792739
|
entity |
| Predicate | notableMentat |
P207353
|
FINISHED |
| Object | Thufir Hawat |
E792734
|
NE 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: Thufir Hawat | Statement: [Mentats, notableMentat, Thufir Hawat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMentat Context triple: [Mentats, notableMentat, Thufir Hawat]
-
A.
notableMonk
Indicates that a person is recognized as a monk of particular significance, prominence, or historical importance.
-
B.
notableMnemonic
Indicates that one entity serves as a well-known or significant mnemonic device for remembering or recalling another entity.
-
C.
notablePriest
Indicates that the subject is recognized as a priest of particular significance or prominence in some context.
-
D.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
E.
notableAbbot
Indicates that a person is recognized as a distinguished or historically significant abbot.
- F. None of above. chosen
Provenance (5 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938af1c0c8190abdcc6a09d84123a |
completed | June 10, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:03 p.m.