Triple
T37588657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581d |
E935193
|
entity |
| Predicate | discoveryObservatory |
P7236
|
FINISHED |
| Object | La Silla Observatory |
—
|
NE NERFINISHED |
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: La Silla Observatory | Statement: [Gliese 581d, discoveryObservatory, La Silla Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryObservatory Context triple: [Gliese 581d, discoveryObservatory, La Silla Observatory]
-
A.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
B.
observatory
chosen
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
C.
observatoryFeature
Indicates that one entity is a feature, component, or characteristic of an observatory.
-
D.
observatoryName
Indicates the name assigned to an observatory.
-
E.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.