Triple
T33689491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | رهط |
E863136
|
entity |
| Predicate | توجد_بالقرب_منها |
P61362
|
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.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
B.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
-
C.
كانت_قريبة_من
Indicates that one entity was physically or metaphorically close to another entity in space, time, or relationship.
-
D.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
E.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:43 a.m.