Triple
T13179274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burst Alert Telescope |
E313681
|
entity |
| Predicate | surveyCapability |
P22290
|
FINISHED |
| Object | all-sky hard X-ray monitoring |
—
|
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: all-sky hard X-ray monitoring | Statement: [Burst Alert Telescope, surveyCapability, all-sky hard X-ray monitoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyCapability Context triple: [Burst Alert Telescope, surveyCapability, all-sky hard X-ray monitoring]
-
A.
surveyFunction
Indicates that an entity serves as a survey-related function or role in relation to another entity or context.
-
B.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
C.
surveyBand
chosen
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
D.
surveyType
Indicates the specific category or kind of survey associated with an entity or activity.
-
E.
surveyName
Indicates the specific name or title assigned to a survey in the context of the relationship.
- 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.