Triple
T18561608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 7 |
E453652
|
entity |
| Predicate | hasOnboardTelescope |
P50657
|
FINISHED |
| Object | astrophysical instruments for X-ray and gamma-ray astronomy |
—
|
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: astrophysical instruments for X-ray and gamma-ray astronomy | Statement: [Salyut 7, hasOnboardTelescope, astrophysical instruments for X-ray and gamma-ray astronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardTelescope Context triple: [Salyut 7, hasOnboardTelescope, astrophysical instruments for X-ray and gamma-ray astronomy]
-
A.
usedOnTelescope
Indicates that something is employed or applied in the operation or functioning of a telescope.
-
B.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
-
C.
telescopeMountedOn
chosen
Indicates that a telescope is physically installed or fixed onto a specific supporting structure or platform.
-
D.
telescopeType
Indicates the specific kind or category of telescope associated with an entity.
-
E.
numberOfTelescopes
Indicates the quantity of telescopes associated with a given entity or 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5380a46f08190afe7ca2ddfe209d5 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:42 a.m.