Triple
T28085920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Herschel Telescope |
E709819
|
entity |
| Predicate | hasSecondaryMirror |
P90082
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [William Herschel Telescope, hasSecondaryMirror, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryMirror Context triple: [William Herschel Telescope, hasSecondaryMirror, yes]
-
A.
hasSecondaryMirrorType
Indicates that an entity’s secondary mirror is of a specified type or design.
-
B.
hasSecondaryMirrorPosition
Indicates the spatial placement or configuration of a secondary mirror relative to the primary optical system.
-
C.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
D.
hasNumberOfPrimaryMirrors
Indicates the relationship specifying how many primary mirrors are associated with a given entity.
-
E.
hasPrimaryMirrorType
Indicates the specific type or design of the primary mirror associated with an optical system or 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 27, 2026, 8:55 p.m.