Triple
T36724851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope Optical Telescope Assembly |
E907164
|
entity |
| Predicate | hasApertureStop |
P196680
|
FINISHED |
| Object | primary mirror edge |
—
|
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: primary mirror edge | Statement: [Hubble Space Telescope Optical Telescope Assembly, hasApertureStop, primary mirror edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApertureStop Context triple: [Hubble Space Telescope Optical Telescope Assembly, hasApertureStop, primary mirror edge]
-
A.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
B.
hasApertureClass
Indicates that one entity is classified according to a specific aperture category or class of another entity.
-
C.
hasApertureShape
Indicates that an entity’s aperture (opening) has a specific geometric or descriptive shape.
-
D.
hasApertureRing
Indicates that one object possesses a physical aperture control ring as a feature or component.
-
E.
minimumAperture
Indicates the smallest opening or aperture size that a system, device, or component can achieve or operate with.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:12 p.m.