Triple
T2748043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaya Nevka |
E60916
|
entity |
| Predicate | isUrbanWaterway |
P41360
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Malaya Nevka, isUrbanWaterway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanWaterway Context triple: [Malaya Nevka, isUrbanWaterway, true]
-
A.
isUrbanRiverOf
Indicates that a river flows through or is located within an urban area associated with a specified place or city.
-
B.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
C.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
D.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
E.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb4ff7b08190b72edb6a2bc5fd19 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:56 p.m.