Triple
T7156600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باب المندب |
E166826
|
entity |
| Predicate | يعد |
P1120
|
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.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
B.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
C.
considered
chosen
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
D.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
E.
consideredIn
Indicates that one entity is taken into account, examined, or included as a factor within the context, scope, or decision framework of another entity.
- 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.