Triple
T25861022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المذهب الحنبلي |
E651476
|
entity |
| Predicate | انتشر تاريخياً في |
P88339
|
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.
historicallyObservedIn
Indicates that something has been recorded or documented as occurring, existing, or taking place within a particular historical context, period, or location.
-
B.
historicalSpread
chosen
Indicates how something has expanded, diffused, or propagated across time and/or space throughout history.
-
C.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
-
D.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
historicalUseInCountry
Indicates that something has been used or practiced within a specific country during a past 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_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_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:05 a.m.