Triple

T31275179
Position Surface form Disambiguated ID Type / Status
Subject กระทรวงกลาโหม E797496 entity
Predicate มีเขตอำนาจ P49097 FINISHED
Object ราชอาณาจักรไทย NE NERFINISHED

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. areaOfAuthority chosen
    Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
  • B. hasAutonomousArea
    Indicates that an entity possesses or contains a geographically or administratively distinct area that has a degree of self-governance or autonomy.
  • C. hasEnforcementArea
    Indicates that an entity is subject to or associated with a specific geographic or jurisdictional area where certain rules, regulations, or enforcement actions apply.
  • D. mayHaveJurisdictionOver
    Indicates that one authority, entity, or body is potentially empowered to exercise legal or official control over another entity, case, or matter.
  • E. hasJurisdictionBoundary
    Indicates that a defined boundary marks the geographic or legal limits within which an authority or jurisdiction has power or control.
  • 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.