Triple
T26727880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama VIII of Thailand |
E673881
|
entity |
| Predicate | regencyCouncil |
P74301
|
FINISHED |
| Object | Council of Regency of Siam |
—
|
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: Council of Regency of Siam | Statement: [Rama VIII of Thailand, regencyCouncil, Council of Regency of Siam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencyCouncil Context triple: [Rama VIII of Thailand, regencyCouncil, Council of Regency of Siam]
-
A.
governingRegency
Indicates that one entity is serving as the regent, exercising governing authority on behalf of another (typically a ruler or state).
-
B.
hasRoyalCouncil
chosen
Indicates that an entity is associated with or governed by a royal council.
-
C.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
-
D.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
E.
regencyFaction
Indicates a political alignment or grouping that supports or is associated with a particular regency or regent authority.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:43 a.m.