Triple
T26509670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELT site at Cerro Armazones |
E669644
|
entity |
| Predicate | telescopeHosted |
P7245
|
FINISHED |
| Object | Extremely Large 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: Extremely Large Telescope | Statement: [ELT site at Cerro Armazones, telescopeHosted, Extremely Large Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeHosted Context triple: [ELT site at Cerro Armazones, telescopeHosted, Extremely Large Telescope]
-
A.
telescopeMountedOn
Indicates that a telescope is physically installed or fixed onto a specific supporting structure or platform.
-
B.
telescopeLocation
chosen
Indicates the physical place or site where a telescope is situated or installed.
-
C.
hostTelescopeAgency
Indicates that an agency is responsible for operating, managing, or hosting a particular telescope.
-
D.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
E.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613906718819093fcde1fceec8bee |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:19 a.m.