Triple
T15829640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGILE gamma-ray mission |
E383835
|
entity |
| Predicate | secondaryBand |
P119802
|
FINISHED |
| Object | hard X-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: hard X-rays | Statement: [AGILE gamma-ray mission, secondaryBand, hard X-rays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBand Context triple: [AGILE gamma-ray mission, secondaryBand, hard X-rays]
-
A.
secondaryLine
Indicates that something serves as a secondary or auxiliary line in relation to a primary or main line.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryBrand
Indicates that one brand is a subordinate, supporting, or less prominent brand in relation to a primary brand.
-
D.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
-
E.
secondaryCircuit
Indicates that one entity functions as the secondary electrical circuit associated with, or derived from, another primary circuit.
- 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.