Triple
T28833006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yedisan |
E728099
|
entity |
| Predicate | majorCityTodayOnTerritory |
P50268
|
FINISHED |
| Object | Odesa |
—
|
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: Odesa | Statement: [Yedisan, majorCityTodayOnTerritory, Odesa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCityTodayOnTerritory Context triple: [Yedisan, majorCityTodayOnTerritory, Odesa]
-
A.
mainCityInTerritory
chosen
Indicates that a city serves as the primary or most important urban center within a specified territory.
-
B.
majorCityInCountry
Indicates that a city is a primary or significant urban center within a specified country.
-
C.
capitalCityObservedIn
Indicates that a particular capital city was observed, recorded, or identified within a specified context, location, or time frame.
-
D.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
E.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 6:38 a.m.