Triple
T28535428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washukanni |
E722149
|
entity |
| Predicate | riverProximityHypothesis |
P8567
|
FINISHED |
| Object | Khabur River |
—
|
NE NERFINISHED |
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: Khabur River | Statement: [Washukanni, riverProximityHypothesis, Khabur River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverProximityHypothesis Context triple: [Washukanni, riverProximityHypothesis, Khabur River]
-
A.
riverBankProximity
Indicates that one entity is located near or adjacent to the bank of a river.
-
B.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
C.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
D.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
E.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 3:31 a.m.