Triple
T16135075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نصب الشهيد |
E391501
|
entity |
| Predicate | يُشرف_على |
P20679
|
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.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
-
B.
oversee
chosen
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
C.
supervisesMinistry
Indicates that one entity has authoritative oversight and managerial responsibility for the operations and activities of a ministry.
-
D.
overseesDivision
Indicates that one entity has managerial or supervisory responsibility over a specific division of an organization.
-
E.
overseesProject
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a04666c819091f36c5a2497d2e7 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.