Triple
T21123468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno |
E520490
|
entity |
| Predicate | radiationMitigation |
P136801
|
FINISHED |
| Object | titanium radiation vault |
—
|
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: titanium radiation vault | Statement: [Juno, radiationMitigation, titanium radiation vault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiationMitigation Context triple: [Juno, radiationMitigation, titanium radiation vault]
-
A.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
B.
majorRadiation
Indicates that one entity is the primary or most significant source of radiation affecting another entity.
-
C.
radiationLevel
Indicates the intensity or amount of radiation present in or emitted by an entity or environment.
-
D.
radiatedFrom
Indicates that something (such as energy, particles, or influence) originates at a source and spreads outward from that source.
-
E.
builtAsMitigationFor
chosen
Indicates that one entity was constructed specifically to reduce, prevent, or counteract a particular risk, problem, or adverse impact associated with another 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.