Triple
T16106369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dajia Jenn Lann Temple |
E390747
|
entity |
| Predicate | worshipService |
P11149
|
FINISHED |
| Object | Mazu worship |
—
|
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: Mazu worship | Statement: [Dajia Jenn Lann Temple, worshipService, Mazu worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipService Context triple: [Dajia Jenn Lann Temple, worshipService, Mazu worship]
-
A.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
B.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipScope
Indicates the range or extent within which worship, veneration, or religious devotion is directed or practiced.
-
E.
worshipLeadership
Indicates that one entity holds a leadership role or primary responsibility in organizing or guiding worship activities for another entity or group.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6d81d081909e1315f4dbfd7369 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.