Triple
T34795670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCOGT telescopes |
E1003072
|
entity |
| Predicate | hasApertureRange |
P2522
|
FINISHED |
| Object | 0.4-meter to 2-meter class |
—
|
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.4-meter to 2-meter class | Statement: [LCOGT telescopes, hasApertureRange, 0.4-meter to 2-meter class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApertureRange Context triple: [LCOGT telescopes, hasApertureRange, 0.4-meter to 2-meter class]
-
A.
hasAperture
Indicates that one entity possesses or is characterized by a specific opening, gap, or aperture.
-
B.
focalLengthRange
Indicates the range of focal lengths over which an optical device (such as a lens) can operate or be adjusted.
-
C.
hasApertureClass
chosen
Indicates that one entity is classified according to a specific aperture category or class of another entity.
-
D.
hasApertureRing
Indicates that one object possesses a physical aperture control ring as a feature or component.
-
E.
hasApertureShape
Indicates that an entity’s aperture (opening) has a specific geometric or descriptive shape.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 3:59 p.m.