Triple
T36661840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avokaya |
E905147
|
entity |
| Predicate | languageUseDomain |
P184483
|
FINISHED |
| Object | home and community communication |
—
|
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: home and community communication | Statement: [Avokaya, languageUseDomain, home and community communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUseDomain Context triple: [Avokaya, languageUseDomain, home and community communication]
-
A.
usesLanguageInDomain
chosen
Indicates that an entity employs a particular language within a specified domain or context (such as a field, discipline, or application area).
-
B.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
C.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
D.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
E.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:11 p.m.