Triple
T11281671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Þingvallavatn |
E267078
|
entity |
| Predicate | hasHydrologicalSource |
P98291
|
FINISHED |
| Object | springs |
—
|
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: springs | Statement: [Þingvallavatn, hasHydrologicalSource, springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydrologicalSource Context triple: [Þingvallavatn, hasHydrologicalSource, springs]
-
A.
hasHydrologicalRegime
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
B.
hasHydrologicalRelation
Indicates a relationship between entities based on the movement, distribution, or connection of water within or between hydrological features or systems.
-
C.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
-
D.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
E.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e96e15708190b3a1cccfbbe65882 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.