Triple
T27494216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubosot |
E693978
|
entity |
| Predicate | locationWithinTemple |
P51530
|
FINISHED |
| Object | central area of temple grounds |
—
|
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: central area of temple grounds | Statement: [Ubosot, locationWithinTemple, central area of temple grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWithinTemple Context triple: [Ubosot, locationWithinTemple, central area of temple grounds]
-
A.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
B.
orientationWithinTemple
Indicates the spatial alignment or directional positioning of something relative to the interior layout of a temple.
-
C.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
-
D.
houseOfTheTempleLocation
Indicates the geographical location where the House of the Temple is situated.
-
E.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: April 27, 2026, 1:07 p.m.