Triple
T29091184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grandmaster |
E734856
|
entity |
| Predicate | planetRuled |
P166303
|
FINISHED |
| Object | Sakaar |
—
|
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: Sakaar | Statement: [Grandmaster, planetRuled, Sakaar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetRuled Context triple: [Grandmaster, planetRuled, Sakaar]
-
A.
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).
-
B.
planetDesignation
Indicates the formal naming or labeling assigned to a planet within a particular cataloging or classification system.
-
C.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
D.
capitalPlanet
Indicates that one planet serves as the capital world or primary governing center for another entity (such as a political or administrative body).
-
E.
zodiacPolarity
Indicates the complementary energetic relationship (positive/negative or active/receptive) associated with a zodiac sign within an astrological system.
- F. None of above. chosen
Provenance (4 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617d89d08190ae38220244c07b1f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 11:05 a.m.