Triple
T7441071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganymede |
E171752
|
entity |
| Predicate | parentPlanetType |
P62562
|
FINISHED |
| Object | gas giant |
—
|
LITERAL FINISHED |
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: gas giant | Statement: [Ganymede, parentPlanetType, gas giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentPlanetType Context triple: [Ganymede, parentPlanetType, gas giant]
-
A.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
-
B.
parentPlanetMassComparison
Indicates a comparison between the mass of a parent planet and the mass of another specified object or body.
-
C.
associatedPlanet
Indicates a relationship where one entity is linked or connected to a particular planet, typically as its relevant or corresponding planetary body.
-
D.
homePlanet
Indicates the planet that serves as the native or original world of an entity.
-
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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f34d84008190936af2b3670ef210 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:13 p.m.