Triple
T34795814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobby–Eberly Telescope |
E1003075
|
entity |
| Predicate | hasScientificInstrument |
P13781
|
FINISHED |
| Object | spectrographs |
—
|
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: spectrographs | Statement: [Hobby–Eberly Telescope, hasScientificInstrument, spectrographs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificInstrument Context triple: [Hobby–Eberly Telescope, hasScientificInstrument, spectrographs]
-
A.
hasObservationInstrument
Indicates that a particular instrument or device was used to make or record an observation.
-
B.
scientificInstruments
chosen
Indicates that one entity is a scientific instrument used by, associated with, or relevant to another entity in the context of scientific measurement or research.
-
C.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
D.
observingInstrument
Indicates that one entity serves as the instrument or device used by another entity to perform an observation.
-
E.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 3:59 p.m.