Triple
T21511614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أمانة العاصمة |
E530737
|
entity |
| Predicate | تقع_في_المنطقة |
P88079
|
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.
takesPlaceInRegion
Indicates that an event or occurrence happens within the boundaries of a specified geographic or administrative region.
-
B.
locatedInTraditionalRegion
chosen
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
C.
meetsInRegion
Indicates that two or more entities encounter or come together within a specified geographic or spatial region.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
endsInRegion
Indicates that an entity’s spatial or temporal extent terminates within the boundaries of a specified region.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea863b18819080e3ff249b10ec28 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.