Triple
T27718413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thale Luang |
E698884
|
entity |
| Predicate | languageUsedInLocalCommunities |
P57300
|
FINISHED |
| Object | Thai |
—
|
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: Thai | Statement: [Thale Luang, languageUsedInLocalCommunities, Thai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInLocalCommunities Context triple: [Thale Luang, languageUsedInLocalCommunities, Thai]
-
A.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
B.
languageLocalCommunities
chosen
Indicates that a language is used, maintained, or holds significance within specific local communities or regions.
-
C.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
D.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
E.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 27, 2026, 3:05 p.m.