Triple

T22827536
Position Surface form Disambiguated ID Type / Status
Subject Bristol Jupiter E565700 entity
Predicate notableVariant P4680 FINISHED
Object Jupiter VIII — NE NERFINISHED

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: Jupiter VIII | Statement: [Bristol Jupiter, notableVariant, Jupiter VIII]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Jupiter VIII
Context triple: [Bristol Jupiter, notableVariant, Jupiter VIII]
  • A. Jupiter XI
    Jupiter XI is the provisional discovery designation for Carme, a retrograde irregular moon of Jupiter.
  • B. Jupiter VII chosen
    Jupiter VII is a specific high-performance variant of the Bristol Jupiter air-cooled radial aircraft engine developed in the interwar period.
  • C. Jupiter Poeninus
    Jupiter Poeninus is a regional form of the Roman god Jupiter venerated in the Alpine areas, particularly associated with mountain passes and local cults.
  • D. Jupiter Pluvius
    Jupiter Pluvius is an aspect of the Roman god Jupiter invoked as the bringer of rain and controller of storms and weather.
  • E. Jupiter Latiaris
    Jupiter Latiaris is an ancient Italic form of the god Jupiter venerated as the chief deity of the Latin peoples, particularly in the Alban Hills near Rome.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2914188190be6cdbd8167cd806 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.