Triple
T25456689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مكة المكرمة |
E637931
|
entity |
| Predicate | كانت مركزاً |
P145012
|
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.
previouslyCenteredOn
Indicates that something was formerly the main focus, reference point, or central subject of another thing, but is no longer in that central position.
-
B.
flourishedAsCulturalCenter
Indicates that a place or community experienced a period of prominence and vitality as a hub of cultural activity, production, and exchange.
-
C.
historicalCenterFor
chosen
Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
-
D.
centered
Indicates that one entity is positioned at or around the central point of another entity or reference frame.
-
E.
developmentCenteredOn
Indicates that the primary focus or core activity of a development process, project, or initiative is oriented around a particular entity or aspect.
- 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.