Triple
T14966365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encke (lunar crater) |
E373197
|
entity |
| Predicate | bestObservedAt |
P20366
|
FINISHED |
| Object | low Sun angle |
—
|
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: low Sun angle | Statement: [Encke (lunar crater), bestObservedAt, low Sun angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestObservedAt Context triple: [Encke (lunar crater), bestObservedAt, low Sun angle]
-
A.
bestObservedWith
chosen
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
B.
observedAt
Indicates that an entity was recorded or noticed at a specific time or place.
-
C.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
D.
isObservedBestFrom
Indicates that something is most favorably or clearly seen, perceived, or measured from a particular viewpoint, location, or context compared to other alternatives.
-
E.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:47 a.m.