Triple
T19321640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowell Discovery Telescope |
E483237
|
entity |
| Predicate | hasGuidingSystem |
P135592
|
FINISHED |
| Object | active optics |
—
|
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: active optics | Statement: [Lowell Discovery Telescope, hasGuidingSystem, active optics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuidingSystem Context triple: [Lowell Discovery Telescope, hasGuidingSystem, active optics]
-
A.
primaryGuidanceSystem
Indicates that one entity functions as the main or principal guidance or navigation system for another entity.
-
B.
guidanceControl
Indicates that one entity directs, manages, or influences the behavior or decisions of another through guidance or control.
-
C.
usesGuideStars
Indicates that an entity relies on guide stars as reference points to perform its operation or achieve accurate positioning.
-
D.
isGuided
Indicates that one entity is being directed, led, or steered in its actions or movement by another entity or influence.
-
E.
hasAutomatedRendezvousSystem
Indicates that an entity is equipped with a system capable of performing rendezvous operations automatically, without direct human control.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d88951081909f7ce6e0610c7258 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.