Triple
T5380239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascanius |
E113063
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Iulus |
E481670
|
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: Iulus | Statement: [Ascanius, alsoKnownAs, Iulus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iulus Context triple: [Ascanius, alsoKnownAs, Iulus]
-
A.
Iulus
chosen
Iulus is a figure in Roman mythology, traditionally regarded as the son of Aeneas and the legendary ancestor of the Julian family, including Julius Caesar.
-
B.
Quintus
Quintus is a traditional Latin praenomen (given name) commonly used in ancient Rome, often indicating the fifth-born child or associated with the number five.
-
C.
Marcius Turbo
Marcius Turbo was a prominent Roman general and governor under Emperor Trajan and Hadrian, noted for his successful military campaigns in the early 2nd century CE.
-
D.
Servius
Servius is a traditional Roman praenomen (given name) used by several notable figures in ancient Rome, including politicians and legendary kings.
-
E.
Gnaeus
Gnaeus is the praenomen (given name) of the prominent Roman general and statesman Pompey the Great.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86ce56c88190a66b3852416edccb |
completed | March 20, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf2949cd9881908ca0d8fdf1642f71 |
completed | March 21, 2026, 11:27 p.m. |
Created at: March 20, 2026, 2:03 p.m.