Triple
T25463036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamazgha |
E638101
|
entity |
| Predicate | linkedToIdentity |
P108480
|
FINISHED |
| Object | Amazigh nationalism |
—
|
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: Amazigh nationalism | Statement: [Tamazgha, linkedToIdentity, Amazigh nationalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToIdentity Context triple: [Tamazgha, linkedToIdentity, Amazigh nationalism]
-
A.
relatedIdentity
chosen
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
B.
modernIdentityLinkedTo
Indicates that an entity’s current or contemporary identity is associated with, derived from, or connected to another entity.
-
C.
linkedByServiceTo
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
D.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
E.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 2:13 p.m.