Triple
T37215646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat Ratchabophit |
E922727
|
entity |
| Predicate | royalTempleType |
P18959
|
FINISHED |
| Object | royal temple of the 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: royal temple of the first class | Statement: [Wat Ratchabophit, royalTempleType, royal temple of the first class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalTempleType Context triple: [Wat Ratchabophit, royalTempleType, royal temple of the 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.
templeComplexFeature
Indicates that one entity is a structural or functional feature that forms part of a larger temple complex.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
E.
shrineType
Indicates the specific category or kind of shrine 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.