Triple
T24590435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dearborn Observatory |
E608516
|
entity |
| Predicate | hasRefractor |
P156470
|
FINISHED |
| Object | large aperture refracting telescope |
—
|
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: large aperture refracting telescope | Statement: [Dearborn Observatory, hasRefractor, large aperture refracting telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefractor Context triple: [Dearborn Observatory, hasRefractor, large aperture refracting telescope]
-
A.
hasRefinery
Indicates that one entity possesses, operates, or is associated with a refinery facility used for processing raw materials.
-
B.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
C.
hasCoronagraph
Indicates that an object or system is equipped with or includes a coronagraph instrument.
-
D.
hasMirrorOrLensMaterial
Indicates that an object’s mirror or lens component is made from a specified material.
-
E.
hasNumberOfNasmythFoci
Indicates the relationship specifying how many Nasmyth foci are associated with a given telescope or optical system.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9da6eb881909b11d4d4cec8e458 |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:30 a.m.