Triple
T9809219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAST |
E238225
|
entity |
| Predicate | supportsMission |
P2186
|
FINISHED |
| Object | Kepler |
E648457
|
NE 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: Kepler | Statement: [MAST, supportsMission, Kepler]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kepler Context triple: [MAST, supportsMission, Kepler]
-
A.
Kepler
Kepler is a prominent lunar impact crater on the Moon’s near side, notable for its bright ray system and relatively young geological age.
-
B.
Kepler
chosen
Kepler was a NASA space telescope mission designed to discover Earth-sized exoplanets by monitoring the brightness of distant stars for transit signals.
-
C.
Keppler
Keppler is a German surname most notably associated with Wilhelm Keppler, an industrialist and early economic adviser to Adolf Hitler.
-
D.
Képler
Képler is a given name associated with the individual known as Pepe.
-
E.
Copernicus
Copernicus is the European Union’s flagship Earth observation programme that uses satellites and ground-based systems to monitor and provide data on the planet’s environment, climate, and security.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc5b4dd8819088c86946b4eb8a39 |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:29 p.m.