Triple
T30619669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | محافظة رأس تنورة |
E779411
|
entity |
| Predicate | تصنف_ك |
P34496
|
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.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
B.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
C.
classificationIntroduced
Indicates that one entity has introduced or established a particular classification or categorization for another entity.
-
D.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
E.
classified
chosen
Indicates that one entity has assigned another entity to a specific category, group, or type based on defined criteria.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689ed5b9c81909976d061f71d782a |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:27 p.m.