Triple
T6054949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hale Telescope |
E134885
|
entity |
| Predicate | wasWorldsLargestOpticalTelescopeUntil |
P52322
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Hale Telescope, wasWorldsLargestOpticalTelescopeUntil, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasWorldsLargestOpticalTelescopeUntil Context triple: [Hale Telescope, wasWorldsLargestOpticalTelescopeUntil, 1976]
-
A.
wasWorldsLargestTelescope
chosen
Indicates that the subject telescope held the status of being the largest telescope in the world during a specified time period.
-
B.
largestTelescopeAperture
Indicates that one entity has the largest telescope aperture (e.g., diameter or area of the primary light-collecting element) among a specified set or context.
-
C.
wasWorldsLargestSingleDishRadioTelescope
Indicates that the subject held the status of being the world’s largest single-dish radio telescope during a particular period.
-
D.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
E.
observatoryName
Indicates the name assigned to an observatory.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570a863c819090291775245708d6 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.