Triple
T25968043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مضائق البحر الأحمر |
E645728
|
entity |
| Predicate | لها_أهمية |
P1887
|
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.
لها
Indicates that something belongs to, is possessed by, or is associated with a feminine or non-human entity.
-
B.
isImportantFor
chosen
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
C.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
D.
importanceInLap
Indicates the degree to which something is significant or influential within a specific lap or iteration of an event or process.
-
E.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604cc423081908edb1fcf694f06fc |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:50 a.m.