Triple

T13761439
Position Surface form Disambiguated ID Type / Status
Subject Julian clan E330618 entity
Predicate claimsDescentFrom P4867 FINISHED
Object Aeneas E110997 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: Aeneas | Statement: [Julian clan, claimsDescentFrom, Aeneas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aeneas
Context triple: [Julian clan, claimsDescentFrom, Aeneas]
  • A. Aeneas chosen
    Aeneas is a Trojan hero in Greco-Roman mythology, renowned as the legendary ancestor of the Romans and the pious protagonist of 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. Turnus
    Turnus is the hot-headed Rutulian prince and chief antagonist of Aeneas in Virgil’s epic poem the Aeneid.
  • D. Anchises
    Anchises is a figure in Greek and Roman mythology best known as the mortal father of the Trojan hero Aeneas and a lover of the goddess Aphrodite.
  • E. Brutus of Troy
    Brutus of Troy is a legendary Trojan exile in medieval British mythology, traditionally credited as the founder and first king of Britain.
  • 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_69d81c573f288190aa2403d484fa3d49 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02250f4881908d5193b3d5d25844 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a8606dbc8190b0f7c38583986141 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:09 p.m.