Triple
T806522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassegrain focus |
E17448
|
entity |
| Predicate | formsFocalPoint |
P9789
|
FINISHED |
| Object | behind the primary mirror |
—
|
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: behind the primary mirror | Statement: [Cassegrain focus, formsFocalPoint, behind the primary mirror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsFocalPoint Context triple: [Cassegrain focus, formsFocalPoint, behind the primary mirror]
-
A.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another entity.
-
B.
formsFeature
chosen
Indicates that one entity constitutes or creates a characteristic, component, or distinguishing element of another entity.
-
C.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
D.
formsSwarms
Indicates that multiple entities come together to create or participate in a coordinated swarm.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.