Triple
T33985029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine |
E871388
|
entity |
| Predicate | hasImportantEconomicZoneIn |
P182436
|
FINISHED |
| Object | Sea of Azov |
—
|
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: Sea of Azov | Statement: [Ukraine, hasImportantEconomicZoneIn, Sea of Azov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantEconomicZoneIn Context triple: [Ukraine, hasImportantEconomicZoneIn, Sea of Azov]
-
A.
isMajorEconomicAreaFor
Indicates that a location or region serves as a primary center of significant economic activity for a specified entity or sector.
-
B.
hasEconomicZoneImplication
Indicates that a relationship or action has consequences for the definition, use, rights, or regulations of an economic zone.
-
C.
hasMajorEconomicRegion
Indicates that an entity includes, is associated with, or is part of a primary or significant economic region within a larger economic or geographic context.
-
D.
isInEconomicZone
Indicates that one entity lies within the designated economic jurisdiction or exclusive economic zone of another entity.
-
E.
hasEconomicZoneType
Indicates the specific classification or category of economic zone associated with an entity.
- 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_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 1, 2026, 1:50 a.m.