Triple
T31184268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthag |
E794991
|
entity |
| Predicate | governingHouseHomeworld |
P9023
|
FINISHED |
| Object | Giedi Prime |
—
|
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: Giedi Prime | Statement: [Carthag, governingHouseHomeworld, Giedi Prime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingHouseHomeworld Context triple: [Carthag, governingHouseHomeworld, Giedi Prime]
-
A.
governmentOnHomeworld
Indicates that a government is established on, or operates from, a particular entity’s homeworld.
-
B.
rulingPlanet
Indicates that one celestial body is considered the primary astrological or mythological governor or influencer of another (such as a zodiac sign or house).
-
C.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
-
D.
homeworldLocation
Indicates the relationship between an entity and the specific place or celestial body that serves as its homeworld.
-
E.
rulingHouse
chosen
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: April 29, 2026, 9:08 p.m.