Triple
T24479417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefwi language |
E617324
|
entity |
| Predicate | sharesGrammarFeaturesWith |
P8039
|
FINISHED |
| Object | Akan |
E54191
|
NE 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: Akan | Statement: [Sefwi language, sharesGrammarFeaturesWith, Akan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesGrammarFeaturesWith Context triple: [Sefwi language, sharesGrammarFeaturesWith, Akan]
-
A.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
B.
hasDialectalFeaturesSharedWith
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
C.
hasGrammaticalSimilarityTo
chosen
Indicates that two linguistic elements share similar grammatical structure, form, or function.
-
D.
linguisticFeature
Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
-
E.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
- F. None of above.
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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed509c88190a0071f8e78b38887 |
completed | April 30, 2026, 12:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ff84bf77c819088cf7601e5ca7e1e |
completed | May 22, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.