Triple
T28085909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Herschel Telescope |
E709819
|
entity |
| Predicate | mirrorSupport |
P50519
|
FINISHED |
| Object | active optics system |
—
|
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: active optics system | Statement: [William Herschel Telescope, mirrorSupport, active optics system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mirrorSupport Context triple: [William Herschel Telescope, mirrorSupport, active optics system]
-
A.
mirrorTechnology
Indicates a relationship where one technology closely reflects, imitates, or duplicates the functionality or design of another.
-
B.
mirrorType
Indicates that one entity is a specific kind or category of mirror in relation to another entity.
-
C.
hasMirrorSupportSystem
chosen
Indicates that an entity is equipped with or connected to a system that supports or stabilizes a mirror.
-
D.
supportsMirrorMode
Indicates that one entity provides the capability for another entity or process to operate in a mirror or mirrored-display mode.
-
E.
mirrorCount
Indicates the number of mirrors associated with or present in relation to a given entity or context.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640659c348190a1c386a3c3904c22 |
completed | May 2, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:55 p.m.