Triple
T12575295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | วัดอรุณราชวรารามราชวรมหาวิหาร |
E300189
|
entity |
| Predicate | มีสถานะ |
P127
|
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.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
C.
possibleStatus
Indicates the set of statuses that an entity is allowed or able to assume within a given context.
-
D.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
typeOfStatus
Indicates the specific status category or condition that an entity is classified as having.
- 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.