Triple
T7456810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinana |
E172145
|
entity |
| Predicate | roleInArabia |
P77018
|
FINISHED |
| Object | major tribal group |
—
|
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: major tribal group | Statement: [Kinana, roleInArabia, major tribal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInArabia Context triple: [Kinana, roleInArabia, major tribal group]
-
A.
roleInUAE
Indicates that an entity holds or has held a specific role, position, or function within the United Arab Emirates.
-
B.
roleInMedina
Indicates the specific function, position, or responsibility an entity holds within the context of Medina.
-
C.
roleInSaudiVision2030
Indicates that an entity has a specific function, responsibility, or contribution within the framework, initiatives, or objectives of Saudi Vision 2030.
-
D.
roleInArabicStudies
Indicates that an entity holds a specific position, function, or involvement within the field or discipline of Arabic studies.
-
E.
roleInPakistan
Indicates that an entity holds or has held a specific role, position, or function within the context of Pakistan.
- F. None of above. chosen
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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3b0780881909e645160dd49eb57 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1ee5ab8819091082324f2dc3b8c |
completed | March 27, 2026, 9:09 p.m. |
Created at: March 27, 2026, 3:15 p.m.