Triple
T29699971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Qādir bi-llāh |
E751454
|
entity |
| Predicate | ruledUnderProtectionOf |
P957
|
FINISHED |
| Object | local Muslim forces |
—
|
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: local Muslim forces | Statement: [al-Qādir bi-llāh, ruledUnderProtectionOf, local Muslim forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledUnderProtectionOf Context triple: [al-Qādir bi-llāh, ruledUnderProtectionOf, local Muslim forces]
-
A.
protectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
D.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
E.
heldToProtect
Indicates that one entity is kept in someone’s possession or custody for the purpose of safeguarding or protecting it.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b3cf608190870b819fff3155b7 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:23 p.m.