Triple
T1528650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsilon Eridani |
E32390
|
entity |
| Predicate | hasPlanetarySystem |
P27660
|
FINISHED |
| Object | candidate |
—
|
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: candidate | Statement: [Epsilon Eridani, hasPlanetarySystem, candidate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanetarySystem Context triple: [Epsilon Eridani, hasPlanetarySystem, candidate]
-
A.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
B.
hasCandidateExoplanets
Indicates that an astronomical object or system is associated with one or more potential exoplanets that meet specified candidacy criteria.
-
C.
hasCandidatePlanet
Indicates that an object (typically a star or system) is associated with a planet that is suspected or proposed to exist but not yet fully confirmed.
-
D.
suspectedPlanetarySystem
chosen
Indicates that an astronomical object is believed, based on available evidence, to host one or more planets but has not yet been confirmed as a planetary system.
-
E.
hasNaturalSatellite
Indicates that one celestial body is orbited by another body that occurs naturally as its satellite.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.