Triple
T18067122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otočac |
E432320
|
entity |
| Predicate | hasLocalRiverCharacteristic |
P128972
|
FINISHED |
| Object | clear karst water of Gacka 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: clear karst water of Gacka River | Statement: [Otočac, hasLocalRiverCharacteristic, clear karst water of Gacka River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalRiverCharacteristic Context triple: [Otočac, hasLocalRiverCharacteristic, clear karst water of Gacka River]
-
A.
hasRiverineCharacteristic
chosen
Indicates that something possesses qualities, features, or conditions associated with rivers or river environments.
-
B.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
C.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cce97ce08190a2f8762ce545e091 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.