Triple
T24921535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tafi Atome |
E618739
|
entity |
| Predicate | hasCommonLinguaFranca |
P24056
|
FINISHED |
| Object | Ewe |
E53601
|
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: Ewe | Statement: [Tafi Atome, hasCommonLinguaFranca, Ewe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonLinguaFranca Context triple: [Tafi Atome, hasCommonLinguaFranca, Ewe]
-
A.
isLinguaFrancaOf
chosen
Indicates that a language serves as a common medium of communication between speakers of different native languages within a particular region, community, or context.
-
B.
hasCommonTranslationLanguage
Indicates that two entities share at least one language into which both can be or have been translated.
-
C.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
D.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
E.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105ccbe3508190813da59d5f373dc1 |
completed | May 22, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 5:28 a.m.