Triple
T37607412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581e |
E935691
|
entity |
| Predicate | belongsToExoplanetCategory |
P201932
|
FINISHED |
| Object | radial-velocity-detected exoplanets |
—
|
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: radial-velocity-detected exoplanets | Statement: [Gliese 581e, belongsToExoplanetCategory, radial-velocity-detected exoplanets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToExoplanetCategory Context triple: [Gliese 581e, belongsToExoplanetCategory, radial-velocity-detected exoplanets]
-
A.
hasExoplanet
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
-
B.
isInPlanetarySystem
Indicates that one celestial object is located within and belongs to a particular planetary system.
-
C.
hasExoplanets
Indicates that the subject celestial system or star possesses one or more confirmed exoplanets in orbit around it.
-
D.
hasStarSystem
Indicates that an entity possesses, contains, or is associated with a particular star system.
-
E.
containsPlanetType
Indicates that one entity includes or encompasses a planet of a specified type within its scope or composition.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
| PDg | Predicate description generation | batch_6a00332d97b88190bafe39ac6f1904ba |
completed | May 10, 2026, 7:26 a.m. |
Created at: May 3, 2026, 4:18 p.m.