Triple
T10539041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معاوية بن أبي سفيان |
E248646
|
entity |
| Predicate | أثر إداري |
P67693
|
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.
administrativeInfluenceOn
Indicates that one entity has the authority or capacity to affect, direct, or shape the administration, management, or governance of another entity.
-
B.
التأثير
chosen
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
C.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
D.
يحكمها
Indicates that an entity governs, rules, or exercises authority over another entity.
-
E.
administeredAs
Indicates that one entity is given or applied to another entity as a treatment, dose, or intervention.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a5730d88190b266a940faf53f65 |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.