Triple
T31104675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Corrino |
E792761
|
entity |
| Predicate | usesPlanetAsPrison |
P122388
|
FINISHED |
| Object | Salusa Secundus |
—
|
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: Salusa Secundus | Statement: [House Corrino, usesPlanetAsPrison, Salusa Secundus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlanetAsPrison Context triple: [House Corrino, usesPlanetAsPrison, Salusa Secundus]
-
A.
inUniversePlanet
Indicates that a planet exists within or belongs to a particular fictional or defined universe.
-
B.
fallPlanet
Indicates that one entity moves downward toward or onto a planetary body, as in falling to or on a planet.
-
C.
usedOnPlanet
chosen
Indicates that something is utilized, applied, or operated on a particular planet.
-
D.
associatedPlanet
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
E.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
- 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_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 9:03 p.m.