Triple
T14111400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferentino |
E339645
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Gavignano |
E108783
|
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: Gavignano | Statement: [Ferentino, sharesBorderWith, Gavignano]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gavignano Context triple: [Ferentino, sharesBorderWith, Gavignano]
-
A.
Gavignano
chosen
Gavignano is a small Italian town in the Lazio region, historically notable as the birthplace of Pope Innocent III.
-
B.
Rapagnano
Rapagnano is a small Italian municipality in the Marche region known for its historic hilltop setting and traditional rural character.
-
C.
Carovigno
Carovigno is a historic town and popular tourist destination in Italy’s Apulia region, known for its medieval castle, olive groves, and proximity to the Adriatic coast.
-
D.
Trevigiani
Trevigiani are the inhabitants or natives of Treviso, a city in the Veneto region of northeastern Italy.
-
E.
Poggiorsini
Poggiorsini is a small Italian town and comune in the Apulia 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600e6a688190a1243a30ae9b7157 |
completed | April 14, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d756bb48190ae5598e48b281f71 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 9, 2026, 10:22 p.m.