Triple
T3905492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idrisid dynasty |
E87193
|
entity |
| Predicate | alliedGroups |
P52816
|
FINISHED |
| Object | local Berber tribes |
—
|
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: local Berber tribes | Statement: [Idrisid dynasty, alliedGroups, local Berber tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedGroups Context triple: [Idrisid dynasty, alliedGroups, local Berber tribes]
-
A.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
B.
alliedDesignation
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
C.
alliedCodeName
Indicates that one entity is known or referred to by a specific code name within an allied or cooperative context.
-
D.
alliedCountries
Indicates that two countries are formally cooperating as allies, typically through mutual support agreements or shared strategic interests.
-
E.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:22 p.m.