Triple
T7426203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaleo Yoovidhya |
E171373
|
entity |
| Predicate | socialStatusAtDeath |
P62272
|
FINISHED |
| Object | one of the richest people in Thailand |
—
|
LITERAL FINISHED |
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: one of the richest people in Thailand | Statement: [Chaleo Yoovidhya, socialStatusAtDeath, one of the richest people in Thailand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusAtDeath Context triple: [Chaleo Yoovidhya, socialStatusAtDeath, one of the richest people in Thailand]
-
A.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
B.
spouseStatusAfterDeath
Indicates the marital status or spousal relationship of a person after the death of their spouse.
-
C.
genealogicalStatus
Indicates the familial or ancestral relationship that one individual has to another within a genealogy.
-
D.
mortalStatus
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
E.
subjectSocialStatus
chosen
Indicates the social standing or rank that the subject holds within a society or group.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f303eb988190ba9df7946fce1c86 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.