Triple
T27717800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athari |
E698867
|
entity |
| Predicate | historicalOpponents |
P22384
|
FINISHED |
| Object | Muʿtazila |
—
|
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: Muʿtazila | Statement: [Athari, historicalOpponents, Muʿtazila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalOpponents Context triple: [Athari, historicalOpponents, Muʿtazila]
-
A.
historicalEnemies
Indicates that the entities have been enemies of each other over a significant period in history.
-
B.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
C.
hasHistoricRivalry
chosen
Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
-
D.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
E.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 27, 2026, 3:05 p.m.