Triple
T8366732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khadjibey |
E197145
|
entity |
| Predicate | nearModernCityCenter |
P34630
|
FINISHED |
| Object | Odesa city center |
—
|
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: Odesa city center | Statement: [Khadjibey, nearModernCityCenter, Odesa city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearModernCityCenter Context triple: [Khadjibey, nearModernCityCenter, Odesa city center]
-
A.
nearDowntown
chosen
Indicates that one location is situated close to or within a short distance of a city’s downtown area.
-
B.
nearModernAvenue
Indicates that one entity is located close to or in the vicinity of a modern avenue.
-
C.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
D.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
E.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808cf80c8190941c3cc0248a5df2 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.