Triple
T25968062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مضائق البحر الأحمر |
E645728
|
entity |
| Predicate | تخضع_ل |
P1313
|
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.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
C.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
D.
indicatesSubjugation
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
E.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
- 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_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:50 a.m.