Triple
T10611564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ava |
E276019
|
entity |
| Predicate | languageCenterOf |
P28898
|
FINISHED |
| Object | Burmese 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: Burmese language | Statement: [Ava, languageCenterOf, Burmese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCenterOf Context triple: [Ava, languageCenterOf, Burmese language]
-
A.
standardLanguageCenter
chosen
Indicates that an entity serves as the primary or officially recognized language center or hub for another entity (such as an organization, region, or system).
-
B.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
C.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
D.
isLinguaFrancaOf
Indicates that a language serves as a common medium of communication between speakers of different native languages within a particular region, community, or context.
-
E.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5a1450819082ad445712fb7868 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.