Triple
T3869328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohře |
E91943
|
entity |
| Predicate | hasGeographicalType |
P12436
|
FINISHED |
| Object | transboundary river |
—
|
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: transboundary river | Statement: [Ohře, hasGeographicalType, transboundary river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicalType Context triple: [Ohře, hasGeographicalType, transboundary river]
-
A.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
B.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
C.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
D.
geographicalRepresentation
Indicates that one entity serves as a geographic depiction, model, or mapping of another entity’s location, area, or spatial characteristics.
-
E.
hasGeologicalProvince
Indicates that a geographic area or location is associated with, or belongs to, a specific geological province characterized by common geological features or history.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec533828819080f52dae15fdbecd |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.