Triple
T4943463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SN 1987A |
E110990
|
entity |
| Predicate | gammaRayLinesDetected |
P60194
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SN 1987A, gammaRayLinesDetected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gammaRayLinesDetected Context triple: [SN 1987A, gammaRayLinesDetected, true]
-
A.
hasBeamlines
Indicates that one entity possesses, contains, or is associated with one or more beamlines.
-
B.
hasXRaySources
Indicates that an entity possesses or is associated with one or more X-ray emitting sources.
-
C.
numberOfDetectors
Indicates the quantity of detectors associated with or involved in a given entity or system.
-
D.
beamLine
Indicates a relationship where one entity directs or projects a beam or focused line (such as light, energy, or signal) toward another entity.
-
E.
dominantEmissionLines
Indicates that the specified emission lines are the most intense or prominent spectral features in the observed emission from an object or region.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff85b50819081d78087caa6b473 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:31 p.m.