Triple
T25895377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afaka syllabary |
E652454
|
entity |
| Predicate | scriptCommunitySize |
P72313
|
FINISHED |
| Object | small number of literate users |
—
|
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: small number of literate users | Statement: [Afaka syllabary, scriptCommunitySize, small number of literate users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCommunitySize Context triple: [Afaka syllabary, scriptCommunitySize, small number of literate users]
-
A.
communitySize
chosen
Indicates the number of individuals or units that make up a given community.
-
B.
usedByCommunitySize
Indicates that something is utilized or adopted by a community characterized by a particular size or number of members.
-
C.
scriptUserCommunity
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
D.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
E.
statusOfCommunity
Indicates the current condition, state, or standing of a community at a given point in time.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 8:22 a.m.