Triple
T7156595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب المندب |
E166826
|
entity |
| Predicate | يستخدم في |
P98
|
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.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
D.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
E.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80dafdc8190b24863b83f084d12 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.