Triple
T30533993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ong Bon Pagoda |
E777088
|
entity |
| Predicate | OngBonRole |
P165140
|
FINISHED |
| Object | protector of merchants |
—
|
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: protector of merchants | Statement: [Ong Bon Pagoda, OngBonRole, protector of merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OngBonRole Context triple: [Ong Bon Pagoda, OngBonRole, protector of merchants]
-
A.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
B.
onamasticRole
Indicates a relationship where an entity holds a specific role or function within the system of naming or onomastics (e.g., as a name-bearer, name-giver, or type of name).
-
C.
roleOnLine1
Indicates that an entity holds a specific role or function associated with the first line of a multi-line structure or sequence.
-
D.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
E.
hogonRole
Indicates that an entity holds or is assigned the role or office of a hogon (a specific traditional or religious leadership position).
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6884eba208190ba177d06a1111541 |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:18 p.m.