Triple
T15637675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler-22b |
E375986
|
entity |
| Predicate | hasFollowUpObservations |
P32415
|
FINISHED |
| Object | ground-based telescopes |
—
|
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: ground-based telescopes | Statement: [Kepler-22b, hasFollowUpObservations, ground-based telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFollowUpObservations Context triple: [Kepler-22b, hasFollowUpObservations, ground-based telescopes]
-
A.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
B.
hasSubsequentTreatment
Indicates that one treatment occurs after and in continuation of another treatment in a temporal sequence.
-
C.
hasLaterInvestigation
Indicates that one investigation occurs after and follows from another in time.
-
D.
followsUp
chosen
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
E.
hasObservationRequirement
Indicates that one entity imposes or specifies an observation-related condition or requirement that must be satisfied by another entity or process.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.