Triple
T27274381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konda River |
E688143
|
entity |
| Predicate | riverCodeType |
P2202
|
FINISHED |
| Object | federal inland waterway of Russia |
—
|
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: federal inland waterway of Russia | Statement: [Konda River, riverCodeType, federal inland waterway of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCodeType Context triple: [Konda River, riverCodeType, federal inland waterway of Russia]
-
A.
riverCodeStatus
Indicates the current regulatory or classification status assigned to a river under a specific coding or standards system.
-
B.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
C.
hasRiverCode
Indicates that a river is associated with a specific identifying code or classification value.
-
D.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to another entity.
-
E.
raceCode
Indicates the classification of an entity according to a standardized race or ethnicity code.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 11:01 a.m.