Triple
T31106241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamis (Dune 2021 film) |
E792799
|
entity |
| Predicate | followsCustomOf |
P186370
|
FINISHED |
| Object | Fremen water-rights tradition |
—
|
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: Fremen water-rights tradition | Statement: [Jamis (Dune 2021 film), followsCustomOf, Fremen water-rights tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCustomOf Context triple: [Jamis (Dune 2021 film), followsCustomOf, Fremen water-rights tradition]
-
A.
followedCustom
chosen
Indicates that one entity chose to follow another entity according to a specific, non-standard or user-defined rule or configuration.
-
B.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
C.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
D.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
E.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
- 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_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 29, 2026, 9:03 p.m.