Triple
T25968014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جزيرة بريم |
E645727
|
entity |
| Predicate | تتحكم_في |
P139391
|
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.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
B.
exertsControlOver
chosen
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
C.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
D.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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.