Triple
T28209961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ذبیحالله مجاهد |
E711131
|
entity |
| Predicate | حوزه نفوذ |
P2828
|
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.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
B.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
C.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
D.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
E.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64310b67481908c2de1bc652d4d87 |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:38 p.m.