Triple
T29362365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Empire |
E744624
|
entity |
| Predicate | controlsPlanet |
P127751
|
FINISHED |
| Object | Trantor |
—
|
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: Trantor | Statement: [Galactic Empire, controlsPlanet, Trantor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPlanet Context triple: [Galactic Empire, controlsPlanet, Trantor]
-
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.
inPlanet
Indicates that one entity is located within or on the planetary body of another entity.
-
C.
capitalPlanet
chosen
Indicates that one planet serves as the capital world or primary governing center for another entity (such as a political or administrative body).
-
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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 2:19 p.m.