Triple
T25860993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أهل السنة والجماعة |
E651475
|
entity |
| Predicate | تاريخيًا_ظهروا_في |
P12102
|
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.
historicallyIn
chosen
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
B.
historicallyManifestedAs
Indicates that one thing has taken shape, been expressed, or become evident in history in the form of another.
-
C.
hasHistoricalContextDisplays
Indicates that something presents or showcases information within a broader historical background or setting.
-
D.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
-
E.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026b467c8190a1f8be336f8679da |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:05 a.m.