Triple
T27233108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of the Bank of Thailand |
E682205
|
entity |
| Predicate | isJudicialRole |
P7038
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Governor of the Bank of Thailand, isJudicialRole, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJudicialRole Context triple: [Governor of the Bank of Thailand, isJudicialRole, false]
-
A.
judicialRole
chosen
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
B.
hasJudicialRank
Indicates that an entity holds a specified level or position within a judicial or court hierarchy.
-
C.
hasJudicialOfficer
Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
-
D.
hasJudgesRole
Indicates that an entity serves in the capacity or role of a judge within a specified context or system.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62650ac7081908ebb09374760e877 |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:47 a.m.