Triple
T34592082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabal Shammar |
E888213
|
entity |
| Predicate | historicalRivalOf |
P22384
|
FINISHED |
| Object | House of Saud |
—
|
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: House of Saud | Statement: [Jabal Shammar, historicalRivalOf, House of Saud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRivalOf Context triple: [Jabal Shammar, historicalRivalOf, House of Saud]
-
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.
hasHistoricRivalry
chosen
Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
-
C.
foundedAsRivalOf
Indicates that an entity was established specifically to compete with or challenge another entity.
-
D.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: May 1, 2026, 2:03 a.m.