Triple
T9809277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K2 mission |
E238226
|
entity |
| Predicate | hostStarTypeCoverage |
P56969
|
FINISHED |
| Object | a wide range of stellar types |
—
|
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: a wide range of stellar types | Statement: [K2 mission, hostStarTypeCoverage, a wide range of stellar types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStarTypeCoverage Context triple: [K2 mission, hostStarTypeCoverage, a wide range of stellar types]
-
A.
hostStarType
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
B.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
C.
hostStarColor
Indicates the color characteristic of a star that serves as the host in the relationship.
-
D.
containsStarType
chosen
Indicates that one entity includes or is associated with a star of a specified stellar type.
-
E.
hostStarActivityLevel
Indicates the intensity or level of stellar activity exhibited by the host star in the relationship or context described.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb21ef32c8190ab4b09d157798451 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.