Triple
T10539042
| 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.
حمله
Indicates an aggressive action in which one entity attacks, assaults, or launches an offensive against another.
-
B.
指揮した戦い
Indicates a relationship where an entity commanded or directed the course of a specific battle.
-
C.
التأثير
chosen
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
D.
nomDeGuerre
Indicates that an entity uses or is known by a pseudonymous or war-related alias instead of their real name.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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.