Triple
T19260859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMB |
E481645
|
entity |
| Predicate | detectedEvent |
P77811
|
FINISHED |
| Object | SN 1987A neutrinos |
—
|
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: SN 1987A neutrinos | Statement: [IMB, detectedEvent, SN 1987A neutrinos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectedEvent Context triple: [IMB, detectedEvent, SN 1987A neutrinos]
-
A.
discoveryEvent
Indicates an event in which something previously unknown or unrecognized is found, identified, or revealed.
-
B.
observedEvent
chosen
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
C.
eventTypeCaptured
Indicates that the specific type or category of an event has been successfully recorded or logged.
-
D.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
E.
eventoDesencadenante
Indicates that one event serves as the trigger or initiating cause for another event or process.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.