Triple
T33751569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omotik language |
E864854
|
entity |
| Predicate | hasVeryFewSpeakers |
P159505
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Omotik language, hasVeryFewSpeakers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVeryFewSpeakers Context triple: [Omotik language, hasVeryFewSpeakers, true]
-
A.
haveLimitedNumberOfSpeakers
chosen
Indicates that the language or communication system is used fluently by only a relatively small number of speakers.
-
B.
speaksRarely
Indicates that the subject speaks infrequently or only on rare occasions.
-
C.
hasNumberOfSpeakersCategory
Indicates a classification of an entity based on the number of speakers associated with it, typically grouping it into predefined size categories.
-
D.
haveSpeakersWhoAre
Indicates that an entity has speakers characterized by a specified property, status, or attribute.
-
E.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:45 a.m.