Triple
T9094958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lez River |
E217992
|
entity |
| Predicate | hasTributaryStatus |
P76971
|
FINISHED |
| Object | primary watercourse for Montpellier area |
—
|
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: primary watercourse for Montpellier area | Statement: [Lez River, hasTributaryStatus, primary watercourse for Montpellier area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTributaryStatus Context triple: [Lez River, hasTributaryStatus, primary watercourse for Montpellier area]
-
A.
hasTributaryType
chosen
Indicates that one watercourse is classified as a specific type of tributary in relation to another water body.
-
B.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
C.
isTributaryDamOf
Indicates that a dam is constructed on and regulates the flow of a tributary river or stream relative to a main watercourse.
-
D.
hasWatershedWith
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
E.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b4a2e0819092f4eae8b1d21f33 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.