Triple
T17661456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FOCAS |
E440261
|
entity |
| Predicate | locatedAtTelescopeFocus |
P97095
|
FINISHED |
| Object | Cassegrain focus |
—
|
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: Cassegrain focus | Statement: [FOCAS, locatedAtTelescopeFocus, Cassegrain focus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtTelescopeFocus Context triple: [FOCAS, locatedAtTelescopeFocus, Cassegrain focus]
-
A.
locationOnTelescope
chosen
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
B.
telescopeLocation
Indicates the physical place or site where a telescope is situated or installed.
-
C.
telescopeFocus
Indicates that one entity adjusts or sets the focal point of a telescope relative to another entity or target.
-
D.
telescopeMountedOn
Indicates that a telescope is physically installed or fixed onto a specific supporting structure or platform.
-
E.
hasCassegrainFocus
Indicates that an optical instrument, typically a telescope, possesses a Cassegrain focus configuration where light is directed to a focal point behind the primary mirror.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea67f8081909da164ca21a98675 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:43 a.m.