Triple
T23199685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 40526 |
E579971
|
entity |
| Predicate | hasPlanetaryCompanion |
P133580
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [HIP 40526, hasPlanetaryCompanion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanetaryCompanion Context triple: [HIP 40526, hasPlanetaryCompanion, yes]
-
A.
hasExoplanet
Indicates that an astronomical object, typically a star, possesses one or more orbiting exoplanets.
-
B.
hasExoplanets
chosen
Indicates that the subject celestial system or star possesses one or more confirmed exoplanets in orbit around it.
-
C.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
D.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
E.
hasPulsarCompanion
Indicates that one astronomical object exists in a bound system with, or is accompanied by, a pulsar.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907835448190aa4fc234d15527c3 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.