Triple
T29514122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akha language |
E748742
|
entity |
| Predicate | spokenAcrossBorders |
P156116
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Akha language, spokenAcrossBorders, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenAcrossBorders Context triple: [Akha language, spokenAcrossBorders, true]
-
A.
spokenInDiaspora
Indicates that a language or dialect is used by a community living outside its original homeland or region of origin.
-
B.
crossBorderLanguage
chosen
Indicates a language that is used across national borders, linking communities in more than one country.
-
C.
includesLanguagesSpokenAlong
Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
-
D.
languageBarrierWith
Indicates that communication between the two entities is hindered or obstructed due to differences in language.
-
E.
crossBorderCommunity
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c61be488190b4a8f39c94a76409 |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:35 p.m.