Triple
T37215645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat Ratchabophit |
E922727
|
entity |
| Predicate | royalTempleClass |
P18959
|
FINISHED |
| Object | first class |
—
|
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: first class | Statement: [Wat Ratchabophit, royalTempleClass, first class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalTempleClass Context triple: [Wat Ratchabophit, royalTempleClass, first class]
-
A.
templeType
chosen
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
lastRulerTempleName
Indicates the name of the temple associated with the most recent or final ruler in a given context.
-
D.
houseOfTheTempleFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a particular temple or house of worship.
-
E.
royalHouseType
Indicates the specific kind or category of royal house associated with an entity (e.g., dynasty, ruling family type, or royal lineage classification).
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.