Triple
T12647222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvius Pertinax the Younger |
E302057
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Helvius |
E967819
|
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: Helvius | Statement: [Helvius Pertinax the Younger, familyName, Helvius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helvius Context triple: [Helvius Pertinax the Younger, familyName, Helvius]
-
A.
Helvius
chosen
Helvius is an ancient Roman family name (nomen) associated with members of the Helvia gens, such as the physician Helvius Successus.
-
B.
Hyllus
Hyllus is a figure in Greek mythology known as the son of Heracles and Deianira, often associated with the Dorian invasion and the Heracleidae.
-
C.
Rigmor
Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
-
D.
Hebrus
Hebrus is the ancient name of the Maritsa River, a major waterway flowing through the Balkans in Southeast Europe.
-
E.
Helmold
Helmold is a Germanic given name, historically used in medieval German-speaking regions and derived from elements meaning "helmet" or "protection" and "rule" or "power."
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9614cefdc81908cfc4a4d04aa6eda |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6687bbb408190b80da2d0310f82c5 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:17 p.m.