Triple
T25456600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بنو هاشم |
E637930
|
entity |
| Predicate | موطن_تاريخي |
P130010
|
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.
historicalHabitat
chosen
Indicates that an entity previously lived, occurred, or was distributed within a particular habitat or environment in the past.
-
B.
otherHistoricSee
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
C.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
D.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
E.
historicalInterest
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of the past.
- 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.