Triple
T34121751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosha |
E875157
|
entity |
| Predicate | usesContactLanguage |
P108903
|
FINISHED |
| Object | Armenian language |
—
|
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: Armenian language | Statement: [Bosha, usesContactLanguage, Armenian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContactLanguage Context triple: [Bosha, usesContactLanguage, Armenian language]
-
A.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
B.
usedAsContactLanguageBetween
Indicates that a language functions as the medium of communication between two or more distinct language communities.
-
C.
usesLanguageFor
chosen
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
D.
primaryLanguageContact
Indicates that one language serves as the main or dominant medium of communication in a particular contact situation between language communities.
-
E.
nationalLanguageContact
Indicates that there is a relationship of linguistic contact or interaction between a national language and another language or language community.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:53 a.m.