Triple
T17038576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anxur |
E413383
|
entity |
| Predicate | hasDeity |
P5606
|
FINISHED |
| Object | Jupiter Anxur |
E413383
|
NE 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: Jupiter Anxur | Statement: [Anxur, hasDeity, Jupiter Anxur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jupiter Anxur Context triple: [Anxur, hasDeity, Jupiter Anxur]
-
A.
Anxur
chosen
Anxur was an important ancient Volscian city in central Italy, later known as Tarracina under Roman rule.
-
B.
Jupiter Pluvius
Jupiter Pluvius is an aspect of the Roman god Jupiter invoked as the bringer of rain and controller of storms and weather.
-
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.
Adrestia
Adrestia is a lesser-known Greek goddess associated with revolt, retribution, and the balance between war and peace.
-
E.
Calisto
Calisto is the young nobleman whose obsessive and tragic love for Melibea drives the plot of the Spanish literary classic *La Celestina*.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f45f84819092cfb27cc33da026 |
completed | April 18, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012338a95c8190951db96209edb61a |
completed | May 11, 2026, 12:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.