Triple
T12575276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | วัดอรุณราชวรารามราชวรมหาวิหาร |
E300189
|
entity |
| Predicate | ตั้งอยู่ริมฝั่ง |
P39043
|
FINISHED |
| Object | ฝั่งธนบุรีของแม่น้ำเจ้าพระยา |
—
|
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: ฝั่งธนบุรีของแม่น้ำเจ้าพระยา | Statement: [วัดอรุณราชวรารามราชวรมหาวิหาร, ตั้งอยู่ริมฝั่ง, ฝั่งธนบุรีของแม่น้ำเจ้าพระยา]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ตั้งอยู่ริมฝั่ง Context triple: [วัดอรุณราชวรารามราชวรมหาวิหาร, ตั้งอยู่ริมฝั่ง, ฝั่งธนบุรีของแม่น้ำเจ้าพระยา]
-
A.
locatedOnBankOfRiver
chosen
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
B.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
D.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
E.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:46 p.m.