Triple
T15881257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jovian ring system |
E385078
|
entity |
| Predicate | mainRingLocation |
P51226
|
FINISHED |
| Object | between Metis and Adrastea orbits |
—
|
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: between Metis and Adrastea orbits | Statement: [Jovian ring system, mainRingLocation, between Metis and Adrastea orbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRingLocation Context triple: [Jovian ring system, mainRingLocation, between Metis and Adrastea orbits]
-
A.
ringLocation
chosen
Indicates the spatial position or placement of a ring relative to a reference object or context.
-
B.
ringOrigin
Indicates the source or starting point from which a ring (such as a circular structure, feature, or formation) arises or is generated.
-
C.
laterFinderOfRing
Indicates that the subject is a subsequent individual who comes into possession of or discovers the ring after an earlier finder.
-
D.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
E.
ringPresentedBy
Indicates that one entity has given or formally presented a ring to 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.