Triple
T13299256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai language |
E316763
|
entity |
| Predicate | hasClassifiers |
P48601
|
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: [Thai language, hasClassifiers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassifiers Context triple: [Thai language, hasClassifiers, true]
-
A.
usesClassifiers
chosen
Indicates that one entity employs or relies on a system of classifiers (such as category labels or measure words) when referring to or organizing another entity.
-
B.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
C.
supportsClassificationUpTo
Indicates that one entity provides assistance, resources, or functionality enabling another entity to perform classification tasks up to a specified level, scope, or complexity.
-
D.
usesClassificationCriteria
Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
-
E.
hasClassifiedTaxon
Indicates that an entity has assigned or associated a specific taxonomic classification to 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.