Triple
T25659247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vai syllabary |
E643330
|
entity |
| Predicate | hasUserCommunitySize |
P72313
|
FINISHED |
| Object | tens of thousands of speakers |
—
|
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: tens of thousands of speakers | Statement: [Vai syllabary, hasUserCommunitySize, tens of thousands of speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserCommunitySize Context triple: [Vai syllabary, hasUserCommunitySize, tens of thousands of speakers]
-
A.
usedByCommunitySize
Indicates that something is utilized or adopted by a community characterized by a particular size or number of members.
-
B.
communitySize
chosen
Indicates the number of individuals or units that make up a given community.
-
C.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
D.
hasGlobalCommunity
Indicates that an entity is associated with or participates in a worldwide community or network of people.
-
E.
hasCommunityGroups
Indicates that an entity is associated with one or more organized community groups or organizations.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faeda57881908a0a6da9de31fc1b |
completed | May 2, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 6:50 p.m.