Triple
T15839647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAXI |
E384067
|
entity |
| Predicate | providesAlertsTo |
P119861
|
FINISHED |
| Object | astronomical community |
—
|
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: astronomical community | Statement: [MAXI, providesAlertsTo, astronomical community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesAlertsTo Context triple: [MAXI, providesAlertsTo, astronomical community]
-
A.
emergencyAlertBrand
Indicates that one entity is the brand or branding associated with an emergency alert system, service, or notification.
-
B.
sharesSignalsIntelligenceWith
Indicates that one entity provides or exchanges signals intelligence (intercepted communications or electronic signals data) with another entity.
-
C.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
D.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.