Triple
T26986926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 22049 |
E679757
|
entity |
| Predicate | solarNeighborhoodMember |
P78600
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HD 22049, solarNeighborhoodMember, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solarNeighborhoodMember Context triple: [HD 22049, solarNeighborhoodMember, true]
-
A.
galacticNeighborhood
Indicates a spatial relationship where one astronomical object or system is located in the nearby region or vicinity of another within a galaxy or local group of galaxies.
-
B.
nearbyToSolarSystem
chosen
Indicates that one astronomical object or region is located at a relatively short distance from the Solar System in space.
-
C.
hasRelationToSun
Indicates a relationship in which an entity is connected or related in some way to the Sun.
-
D.
containsNearestStarSystemToSun
Indicates that the subject set or collection includes the star system that is closest to the Sun.
-
E.
isSolar
Indicates that something is powered by, related to, or derived from the sun or solar energy.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6215ad0848190a7abd513ed22dc44 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:49 a.m.