Triple
T37964639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mu'tamid |
E947103
|
entity |
| Predicate | majorOpponentDynasty |
P69393
|
FINISHED |
| Object | Tulunids |
—
|
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: Tulunids | Statement: [Al-Mu'tamid, majorOpponentDynasty, Tulunids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorOpponentDynasty Context triple: [Al-Mu'tamid, majorOpponentDynasty, Tulunids]
-
A.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
C.
traditionalOpponents
Indicates that two entities customarily or historically compete or conflict with each other as recognized rivals or adversaries.
-
D.
isMajorRivalryFor
chosen
Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
-
E.
hasOpposingTeamsLedBy
Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: May 3, 2026, 4:20 p.m.