Triple
T9341870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caladan |
E224781
|
entity |
| Predicate | politicalStatusAtStartOfDune |
P63481
|
FINISHED |
| Object | fief held by House Atreides |
—
|
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: fief held by House Atreides | Statement: [Caladan, politicalStatusAtStartOfDune, fief held by House Atreides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusAtStartOfDune Context triple: [Caladan, politicalStatusAtStartOfDune, fief held by House Atreides]
-
A.
politicalStatusAtEnd
Indicates the political status or condition an entity holds at the conclusion of a specified event or time period.
-
B.
politicalStatusBefore
chosen
Indicates the political status or condition an entity held prior to a specified event, change, or reference point.
-
C.
politicalStatusBeforeReign
Indicates the political role or status an individual held prior to beginning their reign or period of rule.
-
D.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
E.
politicalStatusAfterEvent
Indicates the political status or condition an entity holds as a result of, or following, a specific event.
- 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bafa9108190889397614756020d |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.