Triple
T32213168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSMOS survey |
E822860
|
entity |
| Predicate | usesSpaceTelescopes |
P8699
|
FINISHED |
| Object | Hubble Space Telescope |
—
|
NE NERFINISHED |
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: Hubble Space Telescope | Statement: [COSMOS survey, usesSpaceTelescopes, Hubble Space Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpaceTelescopes Context triple: [COSMOS survey, usesSpaceTelescopes, Hubble Space Telescope]
-
A.
spaceTelescope
Indicates a relationship where an entity functions as or is classified as a space-based telescope used for astronomical observation beyond Earth's atmosphere.
-
B.
servicedSpaceTelescope
Indicates that an entity has performed maintenance or repair operations on a space telescope.
-
C.
telescopeUsed
chosen
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
D.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
E.
telescopeRole
Indicates the functional role or purpose that a telescope serves within an observation, system, or activity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 12:37 a.m.