Triple
T18174552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hat Creek, California |
E435121
|
entity |
| Predicate | observatoryTypeNearby |
P42053
|
FINISHED |
| Object | radio astronomy observatory |
—
|
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: radio astronomy observatory | Statement: [Hat Creek, California, observatoryTypeNearby, radio astronomy observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observatoryTypeNearby Context triple: [Hat Creek, California, observatoryTypeNearby, radio astronomy observatory]
-
A.
hasNearbyObservatories
chosen
Indicates that one entity has one or more observatories located in close geographic proximity to it.
-
B.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
C.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
D.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
E.
observatoryFeature
Indicates that one entity is a feature, component, or characteristic of an observatory.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df5900788190994525954a89fa3c |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.