Triple
T26825757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taranis |
E675372
|
entity |
| Predicate | hasRomanInterpretatio |
P91771
|
FINISHED |
| Object | Jupiter Taranis |
—
|
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 Taranis | Statement: [Taranis, hasRomanInterpretatio, Jupiter Taranis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanInterpretatio Context triple: [Taranis, hasRomanInterpretatio, Jupiter Taranis]
-
A.
possibleInterpretatioRomana
chosen
Indicates that something can be understood or explained according to a Roman interpretation or in line with Roman cultural, legal, or religious frameworks.
-
B.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
C.
hasRomanEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of Roman culture, naming, or classification.
-
D.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
E.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 4:58 a.m.