Triple
T37588678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581d |
E935193
|
entity |
| Predicate | otherPlanetsInSystem |
P189073
|
FINISHED |
| Object | Gliese 581b |
—
|
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: Gliese 581b | Statement: [Gliese 581d, otherPlanetsInSystem, Gliese 581b]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherPlanetsInSystem Context triple: [Gliese 581d, otherPlanetsInSystem, Gliese 581b]
-
A.
homePlanetSystem
Indicates that one entity is the planetary system that serves as the home or origin system of the other entity.
-
B.
otherMoonsInSystem
Indicates that the entity has one or more moons that share the same planetary or stellar system with it.
-
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.
inPlanet
Indicates that one entity is located within or on the planetary body of another entity.
-
E.
isInPlanetarySystem
Indicates that one celestial object is located within and belongs to a particular planetary system.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.