Triple
T17134762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civiglio |
E415806
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Como city centre |
E1182940
|
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: Como city centre | Statement: [Civiglio, near, Como city centre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Como city centre Context triple: [Civiglio, near, Como city centre]
-
A.
Como city center
chosen
Como city center is the historic and commercial heart of the lakeside city of Como in northern Italy, known for its medieval streets, waterfront promenades, and proximity to Lake Como’s main attractions.
-
B.
City Centre
City Centre is Mississauga’s primary downtown core, known for its high-density residential towers, major shopping complexes, and civic and cultural facilities.
-
C.
City Centre
City Centre is the central commercial and cultural district of Cambridge, known for its historic university buildings, shops, and public spaces.
-
D.
Innenstadt
Innenstadt is the central urban district of Frankfurt am Main, known as the city’s historic core and primary commercial area.
-
E.
Centrum
Centrum is the central district and main urban core of the Dutch municipality of Ridderkerk.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02dca8881908efd73741397a207 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014150d63081908a5614f85694e57a |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.