Triple
T22293863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lemmon Observatory |
E551066
|
entity |
| Predicate | hasClearSkies |
P147955
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mount Lemmon Observatory, hasClearSkies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClearSkies Context triple: [Mount Lemmon Observatory, hasClearSkies, yes]
-
A.
hasSummitClearing
Indicates that an elevated point or summit features an open, cleared area free of significant obstruction.
-
B.
hasNavigationClearance
Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
-
C.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
D.
hasPlatformClearances
Indicates that an entity possesses the necessary permissions or authorizations to access or operate on a specified platform.
-
E.
hasAirspace
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560de3508190951ad0806ae3cc0d |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e75dc7b08081909d64441e979c2fa4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 8:41 p.m.