Triple
T14419942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberon Plateau |
E357555
|
entity |
| Predicate | discoveredOnBodyBy |
P114189
|
FINISHED |
| Object | Voyager 2 imaging |
—
|
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: Voyager 2 imaging | Statement: [Oberon Plateau, discoveredOnBodyBy, Voyager 2 imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredOnBodyBy Context triple: [Oberon Plateau, discoveredOnBodyBy, Voyager 2 imaging]
-
A.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
B.
takenOnBody
Indicates that an item or object is physically carried or worn on a person’s body.
-
C.
bodyDiscoveredIncorrupt
Indicates that a body was found in an unusually preserved or undecayed state, contrary to normal expectations of decomposition.
-
D.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
E.
operatedOnBody
Indicates that a medical or surgical procedure was performed on a particular body or body part.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.