Triple
T25300203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown of Thailand |
E634323
|
entity |
| Predicate | hasCurrentDynasty |
P168024
|
FINISHED |
| Object | Chakri dynasty |
—
|
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: Chakri dynasty | Statement: [Crown of Thailand, hasCurrentDynasty, Chakri dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentDynasty Context triple: [Crown of Thailand, hasCurrentDynasty, Chakri dynasty]
-
A.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
B.
lastReigningDynastyOf
Indicates that one dynasty is the final ruling dynasty to have governed a particular political entity or territory.
-
C.
hasMajorDynasty
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
D.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
E.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
- F. None of above. chosen
Provenance (4 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 21, 2026, 1:24 p.m.