Triple
T3549103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFI wide field imager |
E75066
|
entity |
| Predicate | hostTelescopeType |
P2518
|
FINISHED |
| Object | optical reflecting telescope |
—
|
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: optical reflecting telescope | Statement: [WFI wide field imager, hostTelescopeType, optical reflecting telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostTelescopeType Context triple: [WFI wide field imager, hostTelescopeType, optical reflecting telescope]
-
A.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
B.
hostTelescopeAgency
Indicates that an agency is responsible for operating, managing, or hosting a particular telescope.
-
C.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
D.
hostStarType
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
E.
hostsTelescope
Indicates that one entity provides a location or facility where a telescope is installed, maintained, or operated.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd278348190ad2fa54f4a423541 |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.