Triple
T4797706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Úslava |
E106751
|
entity |
| Predicate | hasAverageDischargeNearMouth |
P59328
|
FINISHED |
| Object | approximately 8 m³/s |
—
|
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: approximately 8 m³/s | Statement: [Úslava, hasAverageDischargeNearMouth, approximately 8 m³/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageDischargeNearMouth Context triple: [Úslava, hasAverageDischargeNearMouth, approximately 8 m³/s]
-
A.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
B.
riverMouthType
Indicates the type or form of the feature where a river meets a larger body of water.
-
C.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
D.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
E.
hasMouthWaterbody
Indicates that a waterbody has a mouth, i.e., the location or feature where it empties or flows into another waterbody or area.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6b3fb598819084a83d2b765a62b0 |
completed | March 20, 2026, 3:43 p.m. |
Created at: March 20, 2026, 1:22 p.m.