Triple
T24921203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sehwi culture |
E618727
|
entity |
| Predicate | relatedEthnicCulture |
P38730
|
FINISHED |
| Object | Akan culture |
—
|
NE NERFINISHED |
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: Akan culture | Statement: [Sehwi culture, relatedEthnicCulture, Akan culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEthnicCulture Context triple: [Sehwi culture, relatedEthnicCulture, Akan culture]
-
A.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
B.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
C.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
D.
hasCulturalRelation
chosen
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
E.
culturalIdentityTiedTo
Indicates that an entity’s cultural identity is closely connected or strongly associated with another specified 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 18, 2026, 5:28 a.m.