Triple
T36251052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Fadl ibn Sahl |
E891802
|
entity |
| Predicate | opposedRivalOfPatron |
P18963
|
FINISHED |
| Object | al-Amin |
—
|
NE NERFINISHED |
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: al-Amin | Statement: [al-Fadl ibn Sahl, opposedRivalOfPatron, al-Amin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedRivalOfPatron Context triple: [al-Fadl ibn Sahl, opposedRivalOfPatron, al-Amin]
-
A.
antagonistOf
chosen
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedRegent
Indicates that one party actively resisted, challenged, or worked against the authority or actions of a regent.
-
D.
typeOfOpposition
Indicates a relationship where one entity stands in opposition or contrast to another, such as being a rival, adversary, or countering force.
-
E.
opposedSuccessor
Indicates that one entity becomes the successor of another in a context of opposition, conflict, or adversarial replacement.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.