Triple
T25968005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جزيرة بريم |
E645727
|
entity |
| Predicate | تقع_بين |
P1262
|
FINISHED |
| Object | خليج عدن |
—
|
NE NERFINISHED |
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.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
takesPlaceBetween
Indicates that an event or interaction occurs within the temporal or spatial interval defined by two reference points.
-
C.
locatedBetweenRivers
Indicates that something is situated in the area or region bounded or flanked by two rivers.
-
D.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
E.
situatedAmong
Indicates that an entity is located within or surrounded by multiple other entities in its immediate environment.
- 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.