Triple
T13179275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burst Alert Telescope |
E313681
|
entity |
| Predicate | onboardSoftwareFunction |
P83486
|
FINISHED |
| Object | real-time burst detection algorithms |
—
|
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: real-time burst detection algorithms | Statement: [Burst Alert Telescope, onboardSoftwareFunction, real-time burst detection algorithms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardSoftwareFunction Context triple: [Burst Alert Telescope, onboardSoftwareFunction, real-time burst detection algorithms]
-
A.
hasOnboardFeature
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
B.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
-
C.
hasSoftwareType
chosen
Indicates that an entity is associated with or classified under a particular type or category of software.
-
D.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
E.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.