Triple
T9206487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zojo-ji Temple |
E220992
|
entity |
| Predicate | denominationHeadTempleOf |
P8490
|
FINISHED |
| Object | Jodo-shu Chinzei branch in the Kanto region |
—
|
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: Jodo-shu Chinzei branch in the Kanto region | Statement: [Zojo-ji Temple, denominationHeadTempleOf, Jodo-shu Chinzei branch in the Kanto region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationHeadTempleOf Context triple: [Zojo-ji Temple, denominationHeadTempleOf, Jodo-shu Chinzei branch in the Kanto region]
-
A.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
B.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
C.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
elementRepresentedByMainTemple
Indicates that a particular element is symbolized or embodied by the main temple in a given religious or cultural context.
-
E.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified 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.