Triple
T37761208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581h |
E941276
|
entity |
| Predicate | rightAscensionRegion |
P131622
|
FINISHED |
| Object | Libra |
—
|
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: Libra | Statement: [Gliese 581h, rightAscensionRegion, Libra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightAscensionRegion Context triple: [Gliese 581h, rightAscensionRegion, Libra]
-
A.
rightAscension
Indicates the angular distance of an object measured eastward along the celestial equator from the vernal equinox, specifying its position in the sky.
-
B.
rightAscensionConstellation
chosen
Indicates that an entity’s right ascension position on the celestial sphere is associated with a specific constellation.
-
C.
rightAscensionRange
Indicates that an entity’s right ascension lies within a specified angular interval on the celestial sphere.
-
D.
containsRightAscension
Indicates that something includes or specifies the right ascension coordinate of an astronomical object or position.
-
E.
hasRightAscensionConstellation
Indicates that an astronomical object’s right ascension places it within a specific constellation.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.