Triple
T16452412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timesitheus |
E399585
|
entity |
| Predicate | nomen |
P744
|
FINISHED |
| Object | Furius |
E1213025
|
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: Furius | Statement: [Timesitheus, nomen, Furius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Furius Context triple: [Timesitheus, nomen, Furius]
-
A.
Furius
chosen
Furius was an ancient Roman family name (nomen) associated with several notable members of the Roman aristocracy.
-
B.
Fannius
Fannius is a character in Cicero’s philosophical dialogue "De re publica," participating in the work’s discussions on Roman politics and constitutional theory.
-
C.
Famedio
Famedio is a grand memorial chapel and pantheon within Milan’s Monumental Cemetery, dedicated to honoring the city’s most illustrious citizens.
-
D.
Noratus
Noratus is a village in Armenia renowned for its ancient cemetery filled with medieval khachkars (carved stone crosses).
-
E.
Urius
Urius was a Roman military commander who played a leading role in the Battle of Strasbourg in 357 CE during Emperor Julian’s campaign against the Alemanni.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce19344819083d323077b742bc3 |
completed | April 18, 2026, 7:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f4e31a08190b121d0cfe2a406c2 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:10 a.m.