Triple
T36127795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-ray astronomy |
E1044929
|
entity |
| Predicate | reasonCannotUseGroundTelescopes |
P196023
|
FINISHED |
| Object | Earth atmosphere absorbs X-rays |
—
|
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: Earth atmosphere absorbs X-rays | Statement: [X-ray astronomy, reasonCannotUseGroundTelescopes, Earth atmosphere absorbs X-rays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonCannotUseGroundTelescopes Context triple: [X-ray astronomy, reasonCannotUseGroundTelescopes, Earth atmosphere absorbs X-rays]
-
A.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
B.
reasonForSelectionAsObservatorySite
Indicates the justification or factors that led to a particular location being chosen as an observatory site.
-
C.
telescopeLocation
Indicates the physical place or site where a telescope is situated or installed.
-
D.
locationOnTelescope
Indicates that one entity is positioned at or attached to a specific part or place on a telescope.
-
E.
benefitForTelescopes
Indicates that something provides an advantage, improvement, or positive effect specifically for telescopes.
- F. None of above. chosen
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: May 3, 2026, 4:08 p.m.