Triple
T19045931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maksutov telescope |
E466130
|
entity |
| Predicate | hasOpticalDesignFeature |
P7246
|
FINISHED |
| Object | all-spherical surfaces |
—
|
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: all-spherical surfaces | Statement: [Maksutov telescope, hasOpticalDesignFeature, all-spherical surfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpticalDesignFeature Context triple: [Maksutov telescope, hasOpticalDesignFeature, all-spherical surfaces]
-
A.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
B.
opticalDesign
chosen
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
C.
hasOpticalChannels
Indicates that an entity possesses one or more optical communication or signal-transmission channels.
-
D.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80466f88190988171920f2be7dc |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.