Triple
T4637460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmidt–Cassegrain telescope design |
E101567
|
entity |
| Predicate | opticalPath |
P7235
|
FINISHED |
| Object | folded optical path |
—
|
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: folded optical path | Statement: [Schmidt–Cassegrain telescope design, opticalPath, folded optical path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalPath Context triple: [Schmidt–Cassegrain telescope design, opticalPath, folded optical path]
-
A.
opticalProperty
Indicates a relationship where an entity has or is characterized by a specific optical property, such as how it interacts with or responds to light.
-
B.
lightPath
chosen
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
C.
opticalDesign
Indicates a relationship where one entity is responsible for creating, specifying, or defining the optical configuration or characteristics of another entity.
-
D.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
E.
rayPattern
Indicates a relationship where something displays or follows a radiating, ray-like arrangement or distribution from a central point.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.