Triple
T11047954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Speech |
E261177
|
entity |
| Predicate | hasLimitedVocabulary |
P97490
|
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: [Black Speech, hasLimitedVocabulary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedVocabulary Context triple: [Black Speech, hasLimitedVocabulary, yes]
-
A.
hasLimitedCorpus
Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
-
B.
hasUncertainVocabulary
Indicates that the relationship involves vocabulary whose meaning, usage, or interpretation is not clearly defined or is subject to doubt.
-
C.
languageCapacity
Indicates the extent to which an entity is able to understand, produce, or otherwise use language.
-
D.
hasLimitedConsonantInventory
Indicates that a language possesses a relatively small set of distinct consonant sounds in its phonological system.
-
E.
hasKnownVocabulary
Indicates that an entity possesses a defined, identifiable set of terms or words that it can recognize or use.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.