Triple
T10163351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atilia |
E233944
|
entity |
| Predicate | nameInLatinAlphabet |
P22444
|
FINISHED |
| Object | Atilia |
E233944
|
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: Atilia | Statement: [Atilia, nameInLatinAlphabet, Atilia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atilia Context triple: [Atilia, nameInLatinAlphabet, Atilia]
-
A.
Atilia
chosen
Atilia was the first wife of the Roman statesman Cato the Younger and the mother of two of his children.
-
B.
Altilia
Altilia is the modern Italian village that encompasses the archaeological remains of the ancient Roman town of Saepinum in the Molise region.
-
C.
Simina
Simina is a surname most notably borne by Wesley W. Simina, a politician from the Federated States of Micronesia.
-
D.
Trisaia
Trisaia is an ENEA research center site in southern Italy known for its activities in energy, environmental, and nuclear technology research.
-
E.
Alessia
Alessia is a feminine given name of Italian origin, notably borne by Canadian singer-songwriter Alessia Cara.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec6a7bb48190952f4318af9cc32b |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d369a120208190b572b61cd6c7da72 |
completed | April 6, 2026, 8:06 a.m. |
Created at: March 30, 2026, 9:09 p.m.