Triple
T15743456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albisola Superiore |
E381655
|
entity |
| Predicate | demonym |
P191
|
FINISHED |
| Object | Albisolesi |
E381655
|
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: Albisolesi | Statement: [Albisola Superiore, demonym, Albisolesi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Albisolesi Context triple: [Albisola Superiore, demonym, Albisolesi]
-
A.
Albisolesi
chosen
Albisolesi are the inhabitants of Albisola Superiore, a town in the Liguria region of northwestern Italy.
-
B.
Albuccione
Albuccione is a frazione (hamlet) of the municipality of Guidonia Montecelio in the Lazio region of central Italy.
-
C.
Alpignano
Alpignano is a town in the Piedmont region of northwestern Italy, located near Turin in the Susa Valley.
-
D.
Caltabellotta
Caltabellotta is a historic hilltop town in Sicily, Italy, known for its medieval architecture and strategic location overlooking the surrounding valleys.
-
E.
Montepeloso
Montepeloso is the historical name of the town now known as Irsina, located in the Basilicata region of southern Italy.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0502c0c3c8190b8e512df307039c1 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff876b7fd081909d84ebe7a4cdb675 |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 4:46 a.m.