Triple
T14512472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الخَابُور |
E340430
|
entity |
| Predicate | نوع_المجرى |
P27890
|
FINISHED |
| Object | نهر دائم الجريان في أجزاء من مساره |
—
|
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: نهر دائم الجريان في أجزاء من مساره | Statement: [الخَابُور, نوع_المجرى, نهر دائم الجريان في أجزاء من مساره]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: نوع_المجرى Context triple: [الخَابُور, نوع_المجرى, نهر دائم الجريان في أجزاء من مساره]
-
A.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
B.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
C.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
D.
hasWatercourseType
chosen
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
E.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.