Triple
T32240783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senussi dynasty |
E823604
|
entity |
| Predicate | tribalBase |
P90920
|
FINISHED |
| Object | Bedouin tribes of Cyrenaica |
—
|
LITERAL 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: Bedouin tribes of Cyrenaica | Statement: [Senussi dynasty, tribalBase, Bedouin tribes of Cyrenaica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalBase Context triple: [Senussi dynasty, tribalBase, Bedouin tribes of Cyrenaica]
-
A.
ethnicOrTribalBase
chosen
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
D.
tribalRoll
Indicates a roll or rotation action performed in a manner characteristic of or associated with a tribe or tribal context.
-
E.
tribalStatus
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:40 a.m.