Triple
T28542134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Słupia River |
E722318
|
entity |
| Predicate | hasMajorPortTownAtMouth |
P414
|
FINISHED |
| Object | Ustka |
—
|
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: Ustka | Statement: [Słupia River, hasMajorPortTownAtMouth, Ustka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPortTownAtMouth Context triple: [Słupia River, hasMajorPortTownAtMouth, Ustka]
-
A.
majorPortAtMouth
chosen
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
B.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
C.
hasMajorSeaPort
Indicates that a place possesses at least one significant seaport used for major maritime transport, trade, or shipping activities.
-
D.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
E.
hasHumanSettlementAtMouth
Indicates that a human settlement is located at the mouth (outflow point) of a geographic feature such as a river or valley.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 28, 2026, 3:36 a.m.