Triple
T17130902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JunoCam |
E415717
|
entity |
| Predicate | radiationEnvironment |
P125804
|
FINISHED |
| Object | high-radiation Jovian environment |
—
|
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: high-radiation Jovian environment | Statement: [JunoCam, radiationEnvironment, high-radiation Jovian environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiationEnvironment Context triple: [JunoCam, radiationEnvironment, high-radiation Jovian environment]
-
A.
radiationLevel
chosen
Indicates the intensity or amount of radiation present in or emitted by an entity or environment.
-
B.
hasRadiationField
Indicates that one entity possesses, generates, or is surrounded by a radiation field associated with another entity.
-
C.
majorRadiation
Indicates that one entity is the primary or most significant source of radiation affecting another entity.
-
D.
radiatedFrom
Indicates that something (such as energy, particles, or influence) originates at a source and spreads outward from that source.
-
E.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f029d1a48190a9d4094827d11d23 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.