Triple
T23199686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 40526 |
E579971
|
entity |
| Predicate | planetarySystemDiscoveryMethod |
P27665
|
FINISHED |
| Object | radial velocity |
—
|
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: radial velocity | Statement: [HIP 40526, planetarySystemDiscoveryMethod, radial velocity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetarySystemDiscoveryMethod Context triple: [HIP 40526, planetarySystemDiscoveryMethod, radial velocity]
-
A.
planetDetectionMethod
chosen
Indicates the method or technique by which a planet was discovered or detected.
-
B.
hasExoplanetsDetected
Indicates that one or more exoplanets have been observed and confirmed to exist in association with the referenced astronomical object.
-
C.
discoveryMethod
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
D.
hasNumberOfConfirmedPlanets
Indicates the relationship that specifies how many planets within a given system or context have been confirmed to exist.
-
E.
numberOfStarsWithPlanets
Indicates the count of stars that have one or more planets associated with them.
- 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.