Triple
T10497136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovilava |
E247566
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Noricum |
E46603
|
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: Noricum | Statement: [Ovilava, locatedIn, Noricum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Noricum Context triple: [Ovilava, locatedIn, Noricum]
-
A.
Noricum
chosen
Noricum was an ancient Celtic kingdom and later a Roman province located in the eastern Alps, roughly corresponding to modern Austria and parts of Slovenia.
-
B.
Raetia
Raetia was a frontier province of the Roman Empire in the central Alps region, covering parts of modern Switzerland, Germany, Austria, and Italy.
-
C.
Moesia Prima
Moesia Prima was a late Roman province located in the central Balkans along the Danube frontier, in what is now mainly eastern Serbia.
-
D.
Moesia Inferior
Moesia Inferior was a Roman province located in the lower Danube region, roughly corresponding to parts of modern-day Bulgaria and Romania.
-
E.
Moesia
Moesia was an ancient Roman province located in the Balkans along the Danube River, encompassing parts of present-day Serbia and Bulgaria.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e343cd76448190b0583cc15005ac9d |
completed | April 18, 2026, 8:41 a.m. |
Created at: April 6, 2026, 12:24 p.m.