Triple
T31275156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | กระทรวงกลาโหม |
E797496
|
entity |
| Predicate | มีหน้าที่ |
P109416
|
FINISHED |
| Object | การป้องกันประเทศ |
—
|
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: การป้องกันประเทศ | Statement: [กระทรวงกลาโหม, มีหน้าที่, การป้องกันประเทศ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: มีหน้าที่ Context triple: [กระทรวงกลาโหม, มีหน้าที่, การป้องกันประเทศ]
-
A.
isTaskedWith
chosen
Indicates that an entity has been assigned the responsibility or duty to perform a specific task or set of tasks.
-
B.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
C.
tieneMisión
Indicates that an entity is assigned or carries out a specific mission or task.
-
D.
performsDuty
Indicates that one entity carries out or fulfills a responsibility, task, or obligation on behalf of or in relation to another entity.
-
E.
mayHaveDuties
Indicates that an entity is potentially subject to certain responsibilities, tasks, or obligations, without asserting that these duties necessarily exist.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.