Triple
T38616967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581f |
E936751
|
entity |
| Predicate | starCatalogDesignationOfHost |
P89571
|
FINISHED |
| Object | GJ 581 |
—
|
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: GJ 581 | Statement: [Gliese 581f, starCatalogDesignationOfHost, GJ 581]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starCatalogDesignationOfHost Context triple: [Gliese 581f, starCatalogDesignationOfHost, GJ 581]
-
A.
hostStarCatalog
Indicates that a celestial object’s host star is listed or identified within a specific astronomical catalog.
-
B.
starKnownAs
chosen
Indicates that a particular star is referred to or identified by a specific name or designation.
-
C.
hostStarHRDesignation
Indicates that a host star is associated with a specific Henry Draper (HR) catalog designation identifying it.
-
D.
hostStarHDDesignation
Indicates that a celestial object’s host star is identified by a specific Henry Draper (HD) catalog designation.
-
E.
usesStarDesignationSystem
Indicates that one entity adopts or applies a particular star designation system to name or classify stars in relation to another entity or context.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.