Triple
T7156572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب المندب |
E166826
|
entity |
| Predicate | أهمية |
P428
|
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.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
B.
significance
chosen
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
C.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
E.
significantAfter
Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
- 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.