Triple
T5013478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJsselmeer |
E112682
|
entity |
| Predicate | previousWaterType |
P21623
|
FINISHED |
| Object | saltwater |
—
|
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: saltwater | Statement: [IJsselmeer, previousWaterType, saltwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousWaterType Context triple: [IJsselmeer, previousWaterType, saltwater]
-
A.
previousHydrologicalType
chosen
Indicates the hydrological classification or condition that applied to a water body or hydrological feature immediately before its current type or state.
-
B.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
C.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
D.
waterServiceType
Indicates the specific kind or category of water service provided or associated with an entity.
-
E.
hasWaterQualityHistory
Indicates that an entity is associated with a record or series of records describing changes or measurements of its water quality over time.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7310c5b08190a5c9ab0f9fe9569f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.