Triple
T27528723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Mirror Telescope |
E694909
|
entity |
| Predicate | originalMirrorDiameter |
P2517
|
FINISHED |
| Object | 1.8 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: 1.8 metres | Statement: [Multiple Mirror Telescope, originalMirrorDiameter, 1.8 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMirrorDiameter Context triple: [Multiple Mirror Telescope, originalMirrorDiameter, 1.8 metres]
-
A.
primaryMirrorDiameter
chosen
Indicates the diameter of the primary mirror used in an optical system or instrument.
-
B.
secondaryMirrorDiameter
Indicates the diameter measurement of a system’s secondary mirror in a multi-mirror optical setup.
-
C.
primaryMirrorShape
Indicates that one entity has a primary mirror whose geometric shape or curvature type is specified by the other entity.
-
D.
primaryMirrorDesignation
Indicates that one entity is designated as the primary mirror (main reflective component) associated with another entity.
-
E.
primaryMirrorCentralHole
Indicates that the primary mirror has a central hole, typically for allowing light or instrumentation to pass through.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 1:25 p.m.