Triple
T25456634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بنو هاشم |
E637930
|
entity |
| Predicate | نظام_اجتماعي_تاريخي |
P33374
|
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.
politicalSystemHistorical
chosen
Indicates a relationship where a political system is characterized or analyzed in terms of its historical development, context, or evolution.
-
B.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
-
C.
historicalRegime
Indicates that one entity functioned as a governing regime or ruling authority over another entity during a specific historical period.
-
D.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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.