Triple
T17683170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta Prohm |
E440819
|
entity |
| Predicate | functionInKhmerEmpire |
P128562
|
FINISHED |
| Object | Buddhist monastery |
—
|
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: Buddhist monastery | Statement: [Ta Prohm, functionInKhmerEmpire, Buddhist monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInKhmerEmpire Context triple: [Ta Prohm, functionInKhmerEmpire, Buddhist monastery]
-
A.
KhmerName
Indicates that the associated name is in the Khmer language or follows Khmer naming conventions.
-
B.
functionInMingDynasty
Indicates that an entity held an official role, position, or function during the Ming Dynasty.
-
C.
hasMeaningInKhmer
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning or interpretation in the Khmer language.
-
D.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704626308190bbdd98d27beb3f24 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.