Triple
T26656955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO Very Large Telescope programme |
E666535
|
entity |
| Predicate | auxiliaryTelescopeDiameter |
P29540
|
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: [ESO Very Large Telescope programme, auxiliaryTelescopeDiameter, 1.8 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auxiliaryTelescopeDiameter Context triple: [ESO Very Large Telescope programme, auxiliaryTelescopeDiameter, 1.8 metres]
-
A.
auxiliaryTelescopeAperture
chosen
Indicates that one entity functions as the auxiliary telescope whose aperture (opening/diameter) is being specified or associated with another entity.
-
B.
hasAuxiliaryTelescopes
Indicates that an entity is equipped with or includes additional telescopes that serve as auxiliary instruments to a primary telescope system.
-
C.
primaryMirrorDiameter
Indicates the diameter of the primary mirror used in an optical system or instrument.
-
D.
secondaryMirrorDiameter
Indicates the diameter measurement of a system’s secondary mirror in a multi-mirror optical setup.
-
E.
twinTelescopeAperture
Indicates that two telescopes share the same aperture size or have apertures that are functionally equivalent.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6168101b881909d4c2c6ca31180a8 |
completed | May 2, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:35 a.m.