Triple
T2977049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transiting Exoplanet Survey Satellite |
E80422
|
entity |
| Predicate | fieldOfViewPerCamera |
P2524
|
FINISHED |
| Object | 24 by 24 degrees |
—
|
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: 24 by 24 degrees | Statement: [Transiting Exoplanet Survey Satellite, fieldOfViewPerCamera, 24 by 24 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfViewPerCamera Context triple: [Transiting Exoplanet Survey Satellite, fieldOfViewPerCamera, 24 by 24 degrees]
-
A.
hasFieldOfView
chosen
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
B.
frontCameraResolution
Indicates the resolution quality or pixel count of a device’s front-facing (selfie) camera.
-
C.
objectiveLensDiameter
Indicates the diameter of the objective lens used in an optical device, such as a camera or telescope.
-
D.
cameraStyle
Indicates the characteristic visual approach or technique used by a camera in capturing or presenting imagery.
-
E.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
- 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_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. |
Created at: March 8, 2026, 2:58 p.m.