Triple
T33931920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بنو أمية |
E869918
|
entity |
| Predicate | موطن_رئيسي_تاريخي |
P17588
|
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.
countryOfHistoricRole
Indicates the country in which an entity held a significant historical role or carried out historically notable activities.
-
B.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
C.
hasMajorHistoricalCentersIn
chosen
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
D.
historicalHabitat
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
E.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.