Triple
T36294049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Shabana |
E893308
|
entity |
| Predicate | relatedTribalConfederation |
P162185
|
FINISHED |
| Object | Shammar |
E257381
|
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 | Statement: [Al Shabana, relatedTribalConfederation, Shammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTribalConfederation Context triple: [Al Shabana, relatedTribalConfederation, Shammar]
-
A.
tribeConfederation
chosen
Indicates a relationship where multiple tribes are united or organized together into a larger confederated group or alliance.
-
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.
involvedTribes
Indicates that there is a relationship specifying which tribes are involved or participating in a particular event, activity, or context.
-
E.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
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_6a3efd9cabb8819087f19b2bc1c125b7 |
completed | June 26, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.