Triple
T33821620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terik language |
E866841
|
entity |
| Predicate | isUsedLessBy |
P19183
|
FINISHED |
| Object | younger Terik generations |
—
|
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: younger Terik generations | Statement: [Terik language, isUsedLessBy, younger Terik generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedLessBy Context triple: [Terik language, isUsedLessBy, younger Terik generations]
-
A.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to another entity.
-
B.
isLessCommonThan
chosen
Indicates that one item occurs, appears, or is observed less frequently than another item.
-
C.
isMoreFrequentlyUsedThan
Indicates that one entity is used or occurs with greater frequency than another entity.
-
D.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
-
E.
isLessCommonSince
Indicates that the frequency or prevalence of one entity has decreased relative to another entity or to its own past occurrence from a specified 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.