Triple
T8917571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valens dynasty |
E212330
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Valens |
E195461
|
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: Valens | Statement: [Valens dynasty, namedAfter, Valens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Valens Context triple: [Valens dynasty, namedAfter, Valens]
-
A.
Valens
chosen
Valens was a 4th-century Roman emperor best known for his reign over the Eastern Roman Empire and his defeat and death at the Battle of Adrianople in 378 AD.
-
B.
Valentin
Valentin is a masculine given name of Latin origin, commonly used in various European and Slavic countries.
-
C.
Veii
Veii was a major ancient Etruscan city in central Italy, known for its wealth, strategic importance, and eventual conquest by Rome in 396 BCE.
-
D.
Evenus
Evenus is a figure in Greek mythology, a king of Aetolia and son of the war god Ares, best known as the father of Marpessa.
-
E.
Verus
Verus was the cognomen of Marcus Annius Verus, a Roman praetor and member of a prominent senatorial family in the 2nd century AD.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1d0965c81908841fe591283e4a4 |
completed | April 3, 2026, 1:34 p.m. |
Created at: March 30, 2026, 6:56 p.m.