Triple
T26330114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medjerda River |
E662357
|
entity |
| Predicate | isPrimaryWaterSourceFor |
P4360
|
FINISHED |
| Object | northern Tunisia |
—
|
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: northern Tunisia | Statement: [Medjerda River, isPrimaryWaterSourceFor, northern Tunisia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryWaterSourceFor Context triple: [Medjerda River, isPrimaryWaterSourceFor, northern Tunisia]
-
A.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
B.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
C.
hasWaterResourceRole
Indicates that an entity participates in a water-related resource context with a specified functional role (e.g., source, user, manager, or regulator of water resources).
-
D.
sourceOfWaterSupply
chosen
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
E.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 26, 2026, 10:33 p.m.