Triple
T7624365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emilian |
E172587
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Romagnol |
E33911
|
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: Romagnol | Statement: [Emilian, closelyRelatedTo, Romagnol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Romagnol Context triple: [Emilian, closelyRelatedTo, Romagnol]
-
A.
Emilian-Romagnol
chosen
Emilian-Romagnol is a Romance language variety spoken primarily in Italy’s Emilia-Romagna region, known for its distinct phonology and vocabulary compared to standard Italian.
-
B.
Brescian
Brescian is a variety of the Lombard language traditionally spoken in and around the city of Brescia in northern Italy.
-
C.
Piacentini
Piacentini are the inhabitants or natives of the Italian city of Piacenza, located in the Emilia-Romagna region.
-
D.
Ferrarese
Ferrarese is a regional variety of the Emilian-Romagnol language spoken in and around the city of Ferrara in northern Italy.
-
E.
Piemontese
Piemontese is a Romance language spoken primarily in Italy’s Piedmont region, distinct from standard Italian and recognized for its own rich literary and cultural tradition.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa6648608190a9203b98b76209aa |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89aa7b264819096ddeda8e4c5ddb4 |
completed | March 29, 2026, 3:21 a.m. |
Created at: March 27, 2026, 3:56 p.m.