Triple
T35724747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat Khun Inthapramun |
E1032576
|
entity |
| Predicate | recliningBuddhaPosition |
P184080
|
FINISHED |
| Object | outdoors |
—
|
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: outdoors | Statement: [Wat Khun Inthapramun, recliningBuddhaPosition, outdoors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recliningBuddhaPosition Context triple: [Wat Khun Inthapramun, recliningBuddhaPosition, outdoors]
-
A.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
-
B.
seatingPosition
Indicates the relative location or arrangement of an entity’s seat with respect to other seats or a reference point in a seating layout.
-
C.
hasSeatingPose
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
-
D.
positionDuringSitting
Indicates the spatial position or posture an entity has specifically while it is in a sitting state.
-
E.
positionInPrayer
Indicates the specific posture or stage a participant occupies within the sequence of actions in a prayer.
- F. None of above. chosen
Provenance (4 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.