Triple
T31184215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremen |
E794990
|
entity |
| Predicate | deityOrSacredFigure |
P150803
|
FINISHED |
| Object | Shai-Hulud |
—
|
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: Shai-Hulud | Statement: [Fremen, deityOrSacredFigure, Shai-Hulud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityOrSacredFigure Context triple: [Fremen, deityOrSacredFigure, Shai-Hulud]
-
A.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
B.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
-
C.
religiousOrMythicFigure
chosen
Indicates that the subject is regarded as a significant figure within a religious tradition or mythological system.
-
D.
guardianDeitiesOrFigures
Indicates a protective or watchful relationship in which certain deities or figures serve as guardians over specific people, places, objects, or domains.
-
E.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with another entity.
- 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_69f224d675d08190957198068e440422 |
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:08 p.m.