Triple
T15839331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeppoSAX |
E384060
|
entity |
| Predicate | firstDetectionOf |
P58918
|
FINISHED |
| Object | X-ray afterglow of GRB 970228 |
—
|
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: X-ray afterglow of GRB 970228 | Statement: [BeppoSAX, firstDetectionOf, X-ray afterglow of GRB 970228]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDetectionOf Context triple: [BeppoSAX, firstDetectionOf, X-ray afterglow of GRB 970228]
-
A.
firstDetectedOn
Indicates the date or time when something was initially observed, discovered, or recorded for the first time.
-
B.
firstObjectDiscovered
Indicates that the referenced object is the earliest one identified or detected in a given context or sequence.
-
C.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
D.
firstEncounteredBy
chosen
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
-
E.
firstTestedBy
Indicates that an item, concept, or process was initially tested or tried out by a particular agent or entity.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e4fa24819086a1a226082ac2d3 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.