Triple
T31103800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Harkonnen |
E792741
|
entity |
| Predicate | formerlyControlled |
P5058
|
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: [House Harkonnen, formerlyControlled, Arrakis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyControlled Context triple: [House Harkonnen, formerlyControlled, Arrakis]
-
A.
historicallyControlledBy
chosen
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
-
B.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
D.
formerlyRegulatedBy
Indicates that an entity was previously subject to the authority or control of a particular regulator, but is no longer regulated by that entity.
-
E.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
- 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_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 29, 2026, 9:03 p.m.