Triple
T2006342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamization of North Africa |
E43594
|
entity |
| Predicate | significantGroup |
P4297
|
FINISHED |
| Object | Arab Muslims |
—
|
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: Arab Muslims | Statement: [Islamization of North Africa, significantGroup, Arab Muslims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantGroup Context triple: [Islamization of North Africa, significantGroup, Arab Muslims]
-
A.
notableSubgroup
chosen
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
majorSegmentOf
Indicates that one entity constitutes a principal or most significant part of another larger whole.
-
D.
typeOfSignificance
Indicates that one entity specifies the nature or category of importance, relevance, or significance that another entity possesses.
-
E.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb898795481909920c1a4c4d62c2d |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.