Triple
T30443723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khmer Krom region |
E774520
|
entity |
| Predicate | historicalNameUsedByKhmer |
P124052
|
FINISHED |
| Object | Kampuchea Krom |
—
|
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: Kampuchea Krom | Statement: [Khmer Krom region, historicalNameUsedByKhmer, Kampuchea Krom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameUsedByKhmer Context triple: [Khmer Krom region, historicalNameUsedByKhmer, Kampuchea Krom]
-
A.
KhmerName
Indicates that the associated name is in the Khmer language or follows Khmer naming conventions.
-
B.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
C.
historicalNameGivenBy
chosen
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
D.
historicalNameUntil
Indicates that an entity bore a particular historical name up to a specified point in time, after which that name was no longer used.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: April 29, 2026, 8:08 p.m.