Triple
T31200848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dune universe |
E795470
|
entity |
| Predicate | centralPlanet |
P52435
|
FINISHED |
| Object | Arrakis |
—
|
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: Arrakis | Statement: [Dune universe, centralPlanet, Arrakis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlanet Context triple: [Dune universe, centralPlanet, Arrakis]
-
A.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
B.
capitalPlanet
Indicates that one planet serves as the capital world or primary governing center for another entity (such as a political or administrative body).
-
C.
innerPlanetOf
Indicates that one celestial body orbits closer to the central star than another body within the same planetary system.
-
D.
inPlanet
Indicates that one entity is located within or on the planetary body of another entity.
-
E.
associatedPlanet
chosen
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 9:09 p.m.