Triple
T147255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIRE |
E3356
|
entity |
| Predicate | opticalDesign |
P7246
|
FINISHED |
| Object | cross-dispersed echellette |
—
|
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: cross-dispersed echellette | Statement: [FIRE, opticalDesign, cross-dispersed echellette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalDesign Context triple: [FIRE, opticalDesign, cross-dispersed echellette]
-
A.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
B.
twinTelescopeAperture
Indicates that two telescopes share the same aperture size or have apertures that are functionally equivalent.
-
C.
primaryMirrorDiameter
Indicates the diameter of the primary mirror used in an optical system or instrument.
-
D.
requiredDesignElement
Indicates that one entity must include, use, or incorporate another entity as a necessary design component or feature.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
- F. None of above. chosen
Provenance (4 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256580c2c8190beecca60ca8595f3 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587e598c81909e1082b813971f48 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.