Triple
T25456702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مكة المكرمة |
E637931
|
entity |
| Predicate | تدار من قبل |
P44469
|
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.
handedDownBy
Indicates that something (such as an object, tradition, or decision) is transferred or passed from one entity to another, typically from an earlier holder or authority to a later recipient.
-
B.
takenBy
Indicates that something is captured, acquired, or received by a particular entity.
-
C.
نزلت_قبل
Indicates that one entity descended, arrived, or was released earlier in time than another entity.
-
D.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
-
E.
governed by
chosen
Indicates that an entity is under the authority, control, or administration of another entity that makes and enforces rules or decisions for it.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.