Triple
T2977057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transiting Exoplanet Survey Satellite |
E80422
|
entity |
| Predicate | surveyCoverage |
P44355
|
FINISHED |
| Object | approximately 85 percent of the sky |
—
|
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: approximately 85 percent of the sky | Statement: [Transiting Exoplanet Survey Satellite, surveyCoverage, approximately 85 percent of the sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyCoverage Context triple: [Transiting Exoplanet Survey Satellite, surveyCoverage, approximately 85 percent of the sky]
-
A.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
B.
surveyType
Indicates the specific category or kind of survey associated with an entity or activity.
-
C.
surveyBand
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
D.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
E.
surveyMethod
Indicates the technique or procedure used to conduct a survey or collect survey data.
- F. None of above. chosen
Provenance (4 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998c589c8190b4530f3fb8975187 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.