Triple
T12176297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASP-96 |
E290094
|
entity |
| Predicate | hostExoplanetType_WASP-96b |
P62562
|
FINISHED |
| Object | hot Saturn-like 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: hot Saturn-like gas giant | Statement: [WASP-96, hostExoplanetType_WASP-96b, hot Saturn-like gas giant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostExoplanetType_WASP-96b Context triple: [WASP-96, hostExoplanetType_WASP-96b, hot Saturn-like gas giant]
-
A.
containsExoplanetHostStars
Indicates that the subject set or collection includes stars that are known to host one or more exoplanets.
-
B.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
-
C.
hasExoplanet
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
-
D.
isExoplanetSearchTarget
Indicates that an astronomical object has been identified as a suitable target for searching for exoplanets.
-
E.
orbitalBodyType
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.