Triple
T19269233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassegrain telescope design |
E481876
|
entity |
| Predicate | hasSecondaryMirrorType |
P135375
|
FINISHED |
| Object | hyperboloidal mirror |
—
|
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: hyperboloidal mirror | Statement: [Cassegrain telescope design, hasSecondaryMirrorType, hyperboloidal mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryMirrorType Context triple: [Cassegrain telescope design, hasSecondaryMirrorType, hyperboloidal mirror]
-
A.
hasSecondaryMirrorPosition
Indicates the spatial placement or configuration of a secondary mirror relative to the primary optical system.
-
B.
hasPrimaryMirrorType
Indicates the specific type or design of the primary mirror associated with an optical system or instrument.
-
C.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
D.
secondaryMirrorDesignation
Indicates the specific label or identifier assigned to a secondary mirror in an optical or telescope system.
-
E.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
- F. None of above. chosen
Provenance (4 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.