Triple
T37845792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Thailand |
E943595
|
entity |
| Predicate | keyMonarch |
P403
|
FINISHED |
| Object | King Ramkhamhaeng of Sukhothai |
—
|
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: King Ramkhamhaeng of Sukhothai | Statement: [History of Thailand, keyMonarch, King Ramkhamhaeng of Sukhothai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMonarch Context triple: [History of Thailand, keyMonarch, King Ramkhamhaeng of Sukhothai]
-
A.
keyRoyalMinister
Indicates that the subject serves as the primary or principal royal minister to the referenced monarch or royal authority.
-
B.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
C.
settingMonarch
Indicates that one entity serves as the reigning monarch or sovereign ruler within the context or setting of another entity.
-
D.
monarch
chosen
Indicates that an entity serves as the sovereign ruler (such as a king, queen, or emperor) over a state or territory.
-
E.
patronMonarch
Indicates a relationship where a monarch acts as a patron, providing support, sponsorship, or protection to another party.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.