Triple
T30810090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Popilia |
E784620
|
entity |
| Predicate | hasModernNameOfConnectedCity |
P20950
|
FINISHED |
| Object | Rimini |
—
|
NE NERFINISHED |
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: Rimini | Statement: [Via Popilia, hasModernNameOfConnectedCity, Rimini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernNameOfConnectedCity Context triple: [Via Popilia, hasModernNameOfConnectedCity, Rimini]
-
A.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
B.
hasModernNearbyCity
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
C.
hasModernName
chosen
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
D.
capitalFoundedModernName
Indicates that the capital city was founded under a different historical name than the one it is known by in modern times.
-
E.
hasAssociatedCityFormerName
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 29, 2026, 8:43 p.m.