Triple
T11889679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meskwaki syllabary |
E282880
|
entity |
| Predicate | scriptUserStatus |
P102089
|
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: [Meskwaki syllabary, scriptUserStatus, small number of literate users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUserStatus Context triple: [Meskwaki syllabary, scriptUserStatus, small number of literate users]
-
A.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
B.
scriptUserCommunity
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
C.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
-
D.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
E.
commandUser
Indicates that one entity issues an instruction or directive that another entity is expected to follow.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a2860c8190a21af5fcddbd2f1e |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.