Triple
T37991530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akan diaspora |
E947830
|
entity |
| Predicate | hasIdentityForm |
P189835
|
FINISHED |
| Object | hyphenated national-Akan identities |
—
|
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: hyphenated national-Akan identities | Statement: [Akan diaspora, hasIdentityForm, hyphenated national-Akan identities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentityForm Context triple: [Akan diaspora, hasIdentityForm, hyphenated national-Akan identities]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
-
C.
hasNationalIdentity
Indicates that an entity possesses or is associated with a particular national identity or nationality.
-
D.
hasIdentityStatus
Indicates that an entity is associated with a particular identity-related state or condition (such as confirmed, provisional, or unknown).
-
E.
hasLegalIdentity
Indicates that an entity is formally recognized as a legal person or subject under the law, with rights and obligations.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.