Triple
T21200952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Ramkhamhaeng (traditional account) |
E522452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical figure (traditional account) |
C772
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical figure (traditional account) Context triple: [King Ramkhamhaeng (traditional account), instanceOf, historical figure (traditional account)]
-
A.
historical figure
chosen
A historical figure is a person from the past whose actions, ideas, or influence significantly shaped events, cultures, or societies and are remembered or studied over time.
-
B.
legendary figure
A legendary figure is a person, real or mythical, whose extraordinary deeds and enduring stories have been magnified and preserved through cultural tradition and collective memory.
-
C.
deified historical figure
A deified historical figure is a once-living person who, through cultural memory and reverence, has been elevated to divine or semi-divine status and worshipped or venerated as a godlike being.
-
D.
historical figure duo
A historical figure duo is a pair of notable individuals from history whose lives, actions, or legacies are closely linked in a way that significantly influenced events or cultural developments.
-
E.
historical ruler
A historical ruler is an individual who held recognized political authority over a state or territory in the past, exercising power to govern, make decisions, and influence the course of history.
- F. None of above.
Provenance (1 batch)
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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:18 p.m.