Triple
T25639096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/2003 J 2 |
E642786
|
entity |
| Predicate | discoveredAtObservatory |
P119853
|
FINISHED |
| Object | Mauna Kea Observatories |
—
|
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: Mauna Kea Observatories | Statement: [S/2003 J 2, discoveredAtObservatory, Mauna Kea Observatories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAtObservatory Context triple: [S/2003 J 2, discoveredAtObservatory, Mauna Kea Observatories]
-
A.
observatoryName
Indicates the name assigned to an observatory.
-
B.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
C.
associatedObservatory
chosen
Indicates that an entity has a relationship with, or is linked to, a particular observatory, such as being operated by, observed at, or otherwise connected to it.
-
D.
observatoryLaunchDate
Indicates the date on which an observatory was officially launched or began its operational activities.
-
E.
observatoryRelocatedFrom
Indicates that an observatory has been moved from a specified original location to a different site.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 5:38 p.m.