Triple
T7235577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agrius |
E155215
|
entity |
| Predicate | hasSibling |
P363
|
FINISHED |
| Object | Latinus |
E105624
|
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: Latinus | Statement: [Agrius, hasSibling, Latinus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Latinus Context triple: [Agrius, hasSibling, Latinus]
-
A.
Latinus
chosen
Latinus is a figure from Greek and Roman mythology, often depicted as a king in Italy associated with the early legends surrounding the founding of Rome.
-
B.
Thascius
Thascius is the family name of the early Christian bishop and martyr Cyprian of Carthage.
-
C.
Romula
Romula was the mother of Roman Emperor Galerius, a peasant woman from Dacia Ripensis who was later honored with significant status during her son's reign.
-
D.
Brunus
Brunus is a Latinized variant of the given name Bruno, historically used in medieval and ecclesiastical contexts.
-
E.
Semo Sancus
Semo Sancus is an ancient Italic god, particularly revered by the Sabines and early Romans as a divine guarantor of oaths, treaties, and good faith.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea33dd3481908ebb050e1fab5aaa |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc32d6c48190ae78b3d1227bb868 |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.