Triple
T31060949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasień |
E791535
|
entity |
| Predicate | isHydronymOfLanguage |
P129739
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Jasień, isHydronymOfLanguage, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHydronymOfLanguage Context triple: [Jasień, isHydronymOfLanguage, Polish]
-
A.
hydronymOf
Indicates that one term is the name of a body of water associated with another geographic entity (e.g., a river, lake, or sea named after a place or feature).
-
B.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
-
C.
watercourseNameLanguage
chosen
Indicates the language in which the name of a watercourse (such as a river or stream) is expressed.
-
D.
hasWatersOf
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
-
E.
hydronymType
Indicates the specific type or category of a water-related geographical name (e.g., river, lake, sea) associated with a hydronym.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:01 p.m.