Triple
T7272531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Bank Telescope |
E161139
|
entity |
| Predicate | azimuthRange |
P32751
|
FINISHED |
| Object | 0 to 360 degrees |
—
|
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: 0 to 360 degrees | Statement: [Green Bank Telescope, azimuthRange, 0 to 360 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: azimuthRange Context triple: [Green Bank Telescope, azimuthRange, 0 to 360 degrees]
-
A.
azimuthCoverage
chosen
Indicates the range or extent of directional angles (azimuths) over which something, such as a sensor or system, provides coverage or operates.
-
B.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
C.
launchAzimuth
Indicates the directional angle or bearing along which a launch (such as a rocket or missile) is initiated relative to a reference direction.
-
D.
rightAscensionRange
Indicates that an entity’s right ascension lies within a specified angular interval on the celestial sphere.
-
E.
angularSize
Indicates the apparent size of an object as seen from a given point, typically measured as the angle it subtends at the observer.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.