Triple
T25750500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler |
E648457
|
entity |
| Predicate | extendedMissionName |
P136783
|
FINISHED |
| Object | K2 |
—
|
NE NERFINISHED |
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: K2 | Statement: [Kepler, extendedMissionName, K2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedMissionName Context triple: [Kepler, extendedMissionName, K2]
-
A.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
B.
continuedMissionOf
chosen
Indicates that one mission is a direct continuation or follow-on of another mission, extending its objectives, activities, or scope over time.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
exampleMission
Indicates that one entity serves as a representative or illustrative mission associated with another entity.
-
E.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 4:34 a.m.