Triple
T36724817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope Optical Telescope Assembly |
E907164
|
entity |
| Predicate | hasSecondaryMirrorDiameter |
P97315
|
FINISHED |
| Object | 0.3 metres |
—
|
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: 0.3 metres | Statement: [Hubble Space Telescope Optical Telescope Assembly, hasSecondaryMirrorDiameter, 0.3 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryMirrorDiameter Context triple: [Hubble Space Telescope Optical Telescope Assembly, hasSecondaryMirrorDiameter, 0.3 metres]
-
A.
secondaryMirrorDiameter
chosen
Indicates the diameter measurement of a system’s secondary mirror in a multi-mirror optical setup.
-
B.
hasSecondaryMirrorType
Indicates that an entity’s secondary mirror is of a specified type or design.
-
C.
hasSecondaryMirrorPosition
Indicates the spatial placement or configuration of a secondary mirror relative to the primary optical system.
-
D.
secondaryMirrorDesignation
Indicates the specific label or identifier assigned to a secondary mirror in an optical or telescope system.
-
E.
primaryMirrorDiameter
Indicates the diameter of the primary mirror used in 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 3, 2026, 4:12 p.m.