Triple
T3615067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler (lunar crater) |
E76579
|
entity |
| Predicate | bestSeenAt |
P31097
|
FINISHED |
| Object | low to moderate telescopic magnification |
—
|
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 to moderate telescopic magnification | Statement: [Kepler (lunar crater), bestSeenAt, low to moderate telescopic magnification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestSeenAt Context triple: [Kepler (lunar crater), bestSeenAt, low to moderate telescopic magnification]
-
A.
bestSeenIn
Indicates that something is most effectively or appropriately experienced, observed, or appreciated within a particular context, medium, or setting.
-
B.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
C.
bestVisitedAt
chosen
Indicates the optimal time or conditions under which a place or entity should be visited.
-
D.
bestObservedWith
Indicates that one entity is most effectively or appropriately observed, detected, or measured when used or considered together with another specified entity.
-
E.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27b5e008190a72a8dab7d736e64 |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.