Triple
T33985038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine |
E871388
|
entity |
| Predicate | majorPortCityOnBlackSea |
P199235
|
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: [Ukraine, majorPortCityOnBlackSea, Odesa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPortCityOnBlackSea Context triple: [Ukraine, majorPortCityOnBlackSea, Odesa]
-
A.
terminusCityOnBlackSea
Indicates that the city serves as a terminus (end point) of a route or connection located on the Black Sea.
-
B.
distanceToBlackSea
Indicates the measured spatial distance between a given entity and the Black Sea.
-
C.
isBalticPortCity
Indicates that a city functions as a port located on the Baltic Sea.
-
D.
capitalOfCountryOfSee
Indicates that one entity is the capital city of the country in which the other entity (a see, typically an episcopal jurisdiction) is located.
-
E.
countryCapitalPort
Indicates that a city serves simultaneously as the capital and a principal port of a given country.
- F. None of above. chosen
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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: May 1, 2026, 1:50 a.m.