Triple
T25679303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasplya |
E643892
|
entity |
| Predicate | riverCodeStatus |
P162595
|
FINISHED |
| Object | international river of Europe |
—
|
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: international river of Europe | Statement: [Kasplya, riverCodeStatus, international river of Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCodeStatus Context triple: [Kasplya, riverCodeStatus, international river of Europe]
-
A.
routeStatus
Indicates the current state or condition of a route, such as whether it is active, available, blocked, or otherwise constrained.
-
B.
hasRiverCode
Indicates that a river is associated with a specific identifying code or classification value.
-
C.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
D.
hasRiverPortStatus
Indicates that an entity holds the status of having a river port, meaning it is officially recognized as a location where river-based shipping or transport operations occur.
-
E.
binaryStatus
Indicates that something has one of two possible states or conditions, typically representing a simple on/off or true/false status.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 21, 2026, 7:45 p.m.