Triple
T33325835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shatt al-Hillah |
E853259
|
entity |
| Predicate | hasHumanSettlementAlongItsBanks |
P56428
|
FINISHED |
| Object | Hillah |
—
|
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: Hillah | Statement: [Shatt al-Hillah, hasHumanSettlementAlongItsBanks, Hillah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanSettlementAlongItsBanks Context triple: [Shatt al-Hillah, hasHumanSettlementAlongItsBanks, Hillah]
-
A.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
B.
hasHumanSettlementAtMouth
Indicates that a human settlement is located at the mouth (outflow point) of a geographic feature such as a river or valley.
-
C.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
D.
hasHumanSettlementAlong
chosen
Indicates that a human settlement is located adjacent to or distributed along the length of a specified geographic feature or route.
-
E.
hasCityOnRiver
Indicates that a city is located on or along the course of a particular river.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.