Triple
T12977690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olza River |
E321570
|
entity |
| Predicate | hasCrossBorderCharacter |
P95603
|
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: [Olza River, hasCrossBorderCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderCharacter Context triple: [Olza River, hasCrossBorderCharacter, true]
-
A.
isCrossBorder
chosen
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
B.
hasCrossBorderInteraction
Indicates that there is an interaction, activity, or relationship occurring between entities located in different countries or jurisdictions.
-
C.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
hasCrossBorderManagement
Indicates that an entity exercises management or control over operations, assets, or activities that extend across national borders.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:38 p.m.