Triple
T28595805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swahili Wiktionary |
E723766
|
entity |
| Predicate | supportsPageCategories |
P203181
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Swahili Wiktionary, supportsPageCategories, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPageCategories Context triple: [Swahili Wiktionary, supportsPageCategories, yes]
-
A.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
B.
supportsSubpages
Indicates that an entity is capable of having and managing subordinate or nested pages beneath it.
-
C.
hasSeparateSupportingCategory
Indicates that an entity is associated with an additional, distinct category used specifically for supporting or auxiliary classification purposes separate from its primary category.
-
D.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
-
E.
supportsDeviceCategory
Indicates that one entity is compatible with and can operate or accommodate a specified category of devices.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
| PDg | Predicate description generation | batch_6a0136e3d6ec8190898b5ab5a628a99d |
completed | May 11, 2026, 1:54 a.m. |
Created at: April 28, 2026, 4:21 a.m.