Triple
T33985030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine |
E871388
|
entity |
| Predicate | hasFishingGroundsIn |
P199767
|
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, hasFishingGroundsIn, Sea of Azov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingGroundsIn Context triple: [Ukraine, hasFishingGroundsIn, Sea of Azov]
-
A.
isFishingArea
Indicates that a location or region is designated or used as an area where fishing activities take place.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
hasShoreFishing
Indicates that a location or body of water provides opportunities or facilities for fishing from the shore.
-
D.
hasFishingBoats
Indicates that one entity possesses, operates, or is associated with one or more fishing boats.
-
E.
hasFishingAccess
Indicates that an entity is permitted or able to fish in or otherwise use a particular water body or fishing area.
- 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_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
| PDg | Predicate description generation | batch_69ff56edc4d081908f1d263e05cbd512 |
completed | May 9, 2026, 3:46 p.m. |
Created at: May 1, 2026, 1:50 a.m.