Triple
T36283137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Sayyah |
E892994
|
entity |
| Predicate | relatedTribalGroup |
P83983
|
FINISHED |
| Object | Shammar of Saudi Arabia |
E2102110
|
NE 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: Shammar of Saudi Arabia | Statement: [Al Sayyah, relatedTribalGroup, Shammar of Saudi Arabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTribalGroup Context triple: [Al Sayyah, relatedTribalGroup, Shammar of Saudi Arabia]
-
A.
hasRelatedTribe
chosen
Indicates that one tribe is associated or connected to another tribe in some relevant way, such as by kinship, alliance, or shared characteristics.
-
B.
associatedTribalNation
Indicates a relationship where an entity is linked or connected to a specific tribal nation, typically reflecting affiliation, relevance, or jurisdiction.
-
C.
associatedTribalGovernment
Indicates a relationship where an entity is formally linked or connected to a specific tribal government.
-
D.
nearTribalGroup
Indicates that one entity is located geographically close to a tribal group.
-
E.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
- F. None of above.
Provenance (4 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e1b3a70819090e811e09330c4ee |
completed | June 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.