Triple
T32019072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernusco sul Naviglio |
E817627
|
entity |
| Predicate | hasCanalSidePromenade |
P12289
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Cernusco sul Naviglio, hasCanalSidePromenade, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalSidePromenade Context triple: [Cernusco sul Naviglio, hasCanalSidePromenade, yes]
-
A.
hasPromenade
chosen
Indicates that one entity features or includes a promenade, typically as a designated walkway or leisure area associated with it.
-
B.
hasPromenadeConnection
Indicates that two locations are linked by a promenade, such as a walkway or pedestrian route, allowing movement or access between them.
-
C.
hasBenchesAlongPromenade
Indicates that benches are present along the length or sides of a promenade.
-
D.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
E.
hasPromenadeStyle
Indicates that something features or is characterized by a particular style or manner associated with promenades or promenade-like walking areas.
- F. None of above.
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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:16 a.m.