Triple
T2786630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai parliament |
E61824
|
entity |
| Predicate | oversightTool |
P15245
|
FINISHED |
| Object | interpellations |
—
|
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: interpellations | Statement: [Thai parliament, oversightTool, interpellations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversightTool Context triple: [Thai parliament, oversightTool, interpellations]
-
A.
oversightTools
chosen
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
B.
oversightFocus
Indicates that one entity’s oversight, supervision, or monitoring activities are specifically directed toward another entity or aspect.
-
C.
oversightScope
Indicates the range or extent of responsibilities and activities that fall under an entity’s oversight or supervisory authority.
-
D.
oversightHistory
Indicates the record of past supervisory or monitoring actions that have been applied to an entity over time.
-
E.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.