Triple
T17095679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karkh District |
E414841
|
entity |
| Predicate | hasSideOfRiver |
P73621
|
FINISHED |
| Object | west bank of the Tigris River |
—
|
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: west bank of the Tigris River | Statement: [Karkh District, hasSideOfRiver, west bank of the Tigris River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideOfRiver Context triple: [Karkh District, hasSideOfRiver, west bank of the Tigris River]
-
A.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
B.
locatedInRiverArea
chosen
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
E.
riverBankOnOneSide
Indicates that a river flows adjacent to and borders only one side of a specified bank or land area.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfdc9c88190b4e75bbdf4105c1e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.