Triple
T30495273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanh Hoa Muong |
E775986
|
entity |
| Predicate | hasSociolinguisticContactWith |
P22730
|
FINISHED |
| Object | Vietnamese 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: Vietnamese language | Statement: [Thanh Hoa Muong, hasSociolinguisticContactWith, Vietnamese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSociolinguisticContactWith Context triple: [Thanh Hoa Muong, hasSociolinguisticContactWith, Vietnamese language]
-
A.
historicalLanguageContact
Indicates that two language communities have been in contact in the past in a way that allowed linguistic influence or exchange between them.
-
B.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
C.
hasSharedBorderHistoryWith
Indicates that two entities have a history of sharing a common border or boundary at some point in time.
-
D.
usedAsContactLanguageBetween
Indicates that a language functions as the medium of communication between two or more distinct language communities.
-
E.
languageContactWith
chosen
Indicates a relationship where two or more languages come into contact through their speakers, leading to interaction and potential mutual influence.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 8:14 p.m.