Triple
T4637482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmidt–Cassegrain telescope design |
E101567
|
entity |
| Predicate | mountCompatibility |
P34359
|
FINISHED |
| Object | alt-azimuth mount |
—
|
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: alt-azimuth mount | Statement: [Schmidt–Cassegrain telescope design, mountCompatibility, alt-azimuth mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountCompatibility Context triple: [Schmidt–Cassegrain telescope design, mountCompatibility, alt-azimuth mount]
-
A.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
B.
migrationCompatibilityWith
Indicates that one entity can be transitioned, upgraded, or moved to another entity or environment without incompatibilities or conflicts.
-
C.
hasHardwareCompatibilityWith
chosen
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
-
E.
compatibilityNote
Indicates that there is an explanatory note or comment about how well two entities are compatible or work together.
- 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.