Triple
T31103758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Atreides |
E792740
|
entity |
| Predicate | keyRetainer |
P36116
|
FINISHED |
| Object | Duncan Idaho |
—
|
NE NERFINISHED |
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: Duncan Idaho | Statement: [House Atreides, keyRetainer, Duncan Idaho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyRetainer Context triple: [House Atreides, keyRetainer, Duncan Idaho]
-
A.
keyHolding
Indicates that one entity possesses and controls access to a key associated with another entity or resource.
-
B.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
C.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
-
D.
keyClient
Indicates that one entity is a primary or strategically important client of another entity.
-
E.
keyOrganizer
chosen
Indicates a relationship where one entity is responsible for managing, arranging, or keeping track of keys for another entity or context.
- 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_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.