Triple
T1471184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etruscans |
E27137
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Vulci |
E94670
|
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: Vulci | Statement: [Etruscans, majorCity, Vulci]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vulci Context triple: [Etruscans, majorCity, Vulci]
-
A.
Vulci
chosen
Vulci was an important ancient Etruscan city renowned for its rich tombs, art, and role in Mediterranean trade.
-
B.
Aurunci
The Aurunci were an ancient Italic people of south-central Italy, known from early Roman history and associated with the Oscan-speaking cultural sphere.
-
C.
Cerveteri
Cerveteri is an ancient Italian town best known as a powerful Etruscan city-state and for its extensive necropolis of rock-cut tombs.
-
D.
Tarquinia
Tarquinia is an ancient Etruscan city in central Italy renowned for its richly painted tombs and significant archaeological remains.
-
E.
Clusium
Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5db55948190ae5262a70a161b87 |
completed | March 1, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad232ab26c8190aa9fc95ff2fcf0eb |
completed | March 8, 2026, 7:20 a.m. |
Created at: March 1, 2026, 8:01 p.m.