Triple
T16594252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insubria |
E403166
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | Insubres |
E295795
|
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: Insubres | Statement: [Insubria, ethnonym, Insubres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Insubres Context triple: [Insubria, ethnonym, Insubres]
-
A.
Insubres
chosen
The Insubres were an ancient Celtic people of northern Italy, centered around Mediolanum (modern Milan), known for their resistance to Roman expansion before eventual incorporation into the Roman Republic.
-
B.
Inunhan
Inunhan is a regional dialect of the Romblomanon language spoken by communities in the province of Romblon in the Philippines.
-
C.
Isanzu
Isanzu is a Bantu language spoken by the Isanzu people of north-central Tanzania.
-
D.
Rascia
Rascia is a historical region in the central Balkans that formed the medieval core of the Serbian state.
-
E.
Iturea
Iturea was an ancient region in the Levant, inhabited by the Itureans and later incorporated into various Hellenistic and Roman client kingdoms, including those ruled by the Herodian dynasty.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d70ad008190bba0901bf3c7089f |
completed | April 18, 2026, 10:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00759dea5c819083fe9fb7dee37a35 |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:16 a.m.