Triple
T15829639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGILE gamma-ray mission |
E383835
|
entity |
| Predicate | primaryBand |
P119801
|
FINISHED |
| Object | gamma rays |
—
|
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: gamma rays | Statement: [AGILE gamma-ray mission, primaryBand, gamma rays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBand Context triple: [AGILE gamma-ray mission, primaryBand, gamma rays]
-
A.
previousBand
Indicates that one musical group was a band that a person or entity was a member of or involved with before their current band.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
D.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
E.
band
Indicates that multiple entities join together to form a unified group, typically for a shared purpose or activity.
- 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_69e11e62aba8819090978801f4df73fe |
completed | April 16, 2026, 5:37 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.