Triple
T965493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magellan Clay Telescope |
E20827
|
entity |
| Predicate | telescopeClass |
P2518
|
FINISHED |
| Object | large-aperture research 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: large-aperture research telescope | Statement: [Magellan Clay Telescope, telescopeClass, large-aperture research telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeClass Context triple: [Magellan Clay Telescope, telescopeClass, large-aperture research telescope]
-
A.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
B.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
C.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
D.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
E.
telescopeLocation
Indicates the physical place or site where a telescope is situated or installed.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b431d61481908b53490e99670363 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.