Triple
T19269227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassegrain telescope design |
E481876
|
entity |
| Predicate | hasOpticalPath |
P7239
|
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: [Cassegrain telescope design, hasOpticalPath, folded optical path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpticalPath Context triple: [Cassegrain telescope design, hasOpticalPath, folded optical path]
-
A.
hasOpticalElement
Indicates that one entity includes, contains, or is equipped with a specific optical element as a component or part.
-
B.
hasOpticalChannels
Indicates that an entity possesses one or more optical communication or signal-transmission channels.
-
C.
usesOpticsType
chosen
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
D.
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.
-
E.
hasFocalPlane
Indicates that an optical system or imaging device possesses a specific focal plane where light is brought into focus.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.