Triple
T38105449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butsuden |
E951497
|
entity |
| Predicate | hasPositionInTempleLayout |
P51530
|
FINISHED |
| Object | central building of the temple complex |
—
|
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 building of the temple complex | Statement: [Butsuden, hasPositionInTempleLayout, central building of the temple complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInTempleLayout Context triple: [Butsuden, hasPositionInTempleLayout, central building of the temple complex]
-
A.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
B.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
C.
orientationWithinTemple
Indicates the spatial alignment or directional positioning of something relative to the interior layout of a temple.
-
D.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
-
E.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:21 p.m.