Triple
T30289384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariminus River |
E770329
|
entity |
| Predicate | hasModernCityRelation |
P85999
|
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: [Ariminus River, hasModernCityRelation, Rimini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernCityRelation Context triple: [Ariminus River, hasModernCityRelation, Rimini]
-
A.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
B.
modernMunicipalityRelation
chosen
Indicates a relationship where one entity corresponds to, or is part of, the modern municipal jurisdiction associated with another entity.
-
C.
hasModernNearbyCity
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
D.
hasUrbanRelation
Indicates a relationship where one entity is connected to another through an urban context, such as city-based location, influence, or interaction.
-
E.
refersToModernCity
Indicates that one entity is a reference to, or designation for, a contemporary city in the modern world.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:47 p.m.