Triple
T26535539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Astronomical Observatory |
E671233
|
entity |
| Predicate | operatedTelescopeType |
P2518
|
FINISHED |
| Object | optical telescope |
—
|
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: optical telescope | Statement: [Tokyo Astronomical Observatory, operatedTelescopeType, optical telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedTelescopeType Context triple: [Tokyo Astronomical Observatory, operatedTelescopeType, optical telescope]
-
A.
telescopeType
chosen
Indicates the specific kind or category of telescope associated with an entity.
-
B.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
C.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
D.
observingInstrument
Indicates that one entity serves as the instrument or device used by another entity to perform an observation.
-
E.
notableTelescope
Indicates that the subject is a telescope recognized for its significance, prominence, or special importance in some context.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 27, 2026, 1:38 a.m.