Triple
T26657081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VISTA Hemisphere Survey |
E666538
|
entity |
| Predicate | telescopeSiteOperator |
P7237
|
FINISHED |
| Object | European Southern 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: European Southern Observatory | Statement: [VISTA Hemisphere Survey, telescopeSiteOperator, European Southern Observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telescopeSiteOperator Context triple: [VISTA Hemisphere Survey, telescopeSiteOperator, European Southern Observatory]
-
A.
observatoryOperator
chosen
Indicates that one entity operates, manages, or runs an observatory facility for another entity or in an official capacity.
-
B.
observatoryName
Indicates the name assigned to an observatory.
-
C.
telescopeRole
Indicates the functional role or purpose that a telescope serves within an observation, system, or activity.
-
D.
observatoryOrganization
Indicates that an organization operates, manages, or is institutionally responsible for an observatory.
-
E.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:35 a.m.