Triple
T30903055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khvarshi |
E787221
|
entity |
| Predicate | usedAsL2With |
P193313
|
FINISHED |
| Object | Avar language |
—
|
NE NERFINISHED |
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: Avar language | Statement: [Khvarshi, usedAsL2With, Avar language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsL2With Context triple: [Khvarshi, usedAsL2With, Avar language]
-
A.
usedAsL2By
Indicates that something serves as a second language (L2) for a particular user or group of users.
-
B.
L2Is
Indicates that one entity is located at or occupies a specific level 2 (L2) position or layer relative to another entity.
-
C.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 29, 2026, 8:50 p.m.