Triple
T9206496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zojo-ji Temple |
E220992
|
entity |
| Predicate | isReligiousCenter |
P23109
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zojo-ji Temple, isReligiousCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReligiousCenter Context triple: [Zojo-ji Temple, isReligiousCenter, true]
-
A.
isCentralToReligion
Indicates that something plays a core, defining, or foundational role within a particular religion or religious tradition.
-
B.
tookPlaceAtReligiousCenter
Indicates that an event or action occurred at a religious center or place of worship.
-
C.
ecclesiasticalCenter
chosen
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
hasReligiousHeadquarters
Indicates that an organization or religious group has its main religious administrative center or headquarters located at a specific place.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b0b6788190908bee67a0c5d48f |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.