Triple
T28289457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Telescopio Canarias |
E713381
|
entity |
| Predicate | openedToAstronomers |
P41299
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Gran Telescopio Canarias, openedToAstronomers, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToAstronomers Context triple: [Gran Telescopio Canarias, openedToAstronomers, 2009]
-
A.
observatoryOpened
chosen
Indicates that an observatory has begun operating or has been officially opened for use.
-
B.
isLinkedToAstronomy
Indicates that something has a connection or relevant association to the field or study of astronomy.
-
C.
observatoryContribution
Indicates a relationship where an entity contributes to, supports, or participates in the operation, development, or activities of an observatory.
-
D.
hasDiscoveredAstronomicalObject
Indicates that an entity has identified and confirmed the existence of a previously unknown astronomical object.
-
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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 11:28 p.m.