Triple
T31263098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngahtatgyi Buddha Temple |
E797174
|
entity |
| Predicate | hasSeatingPosture |
P55537
|
FINISHED |
| Object | Buddha in bhumisparsha mudra (earth-touching gesture) |
—
|
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: Buddha in bhumisparsha mudra (earth-touching gesture) | Statement: [Ngahtatgyi Buddha Temple, hasSeatingPosture, Buddha in bhumisparsha mudra (earth-touching gesture)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatingPosture Context triple: [Ngahtatgyi Buddha Temple, hasSeatingPosture, Buddha in bhumisparsha mudra (earth-touching gesture)]
-
A.
hasSeatingPose
chosen
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
-
B.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
hasBackrest
Indicates that one entity (typically a seat or seating object) includes or is equipped with a supporting backrest.
-
E.
canSitIn
Indicates that one entity is able or permitted to sit inside or occupy the seating space of another 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: April 29, 2026, 9:12 p.m.