Triple
T19468950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutulian |
E487070
|
entity |
| Predicate | notableMember |
P10
|
FINISHED |
| Object | Turnus |
—
|
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: Turnus | Statement: [Rutulian, notableMember, Turnus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Turnus Context triple: [Rutulian, notableMember, Turnus]
-
A.
Turnus
chosen
Turnus is the hot-headed Rutulian prince and chief antagonist of Aeneas in Virgil’s epic poem the Aeneid.
-
B.
Ascanius
Ascanius is the legendary son of Aeneas in Roman mythology, regarded as an ancestor of the founders of Rome and a symbol of its destined imperial future.
-
C.
Montillus
Montillus is a masculine given name, most notably borne by Montillus Murray Beatty.
-
D.
Caeneus
Caeneus is a figure from Greek mythology who was originally a woman named Caenis, transformed into an invulnerable male warrior and famed member of the Lapiths.
-
E.
Tullus Hostilius
Tullus Hostilius was the legendary third king of Rome, traditionally remembered for his warlike reign and the destruction of Alba Longa.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e4b230819097c8804ee91988ea |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 10, 2026, 1:39 p.m.