Triple
T37148124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villesi |
E920294
|
entity |
| Predicate | associatedWithNearbyCity |
P25162
|
FINISHED |
| Object | Reggio Calabria |
E140141
|
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: Reggio Calabria | Statement: [Villesi, associatedWithNearbyCity, Reggio Calabria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNearbyCity Context triple: [Villesi, associatedWithNearbyCity, Reggio Calabria]
-
A.
hasNearbyCityArea
Indicates that one area is geographically close to or adjacent to a city area.
-
B.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
-
C.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
D.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
E.
associatedCityCode
Indicates that an entity is linked or related to a specific city identified by its code.
- F. None of above.
Provenance (4 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406cc3ac5c8190987c9327df8ad389 |
completed | June 28, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.