Triple
T26949907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haeinsa |
E678751
|
entity |
| Predicate | otherThreeJewelTemples |
P167308
|
FINISHED |
| Object | Tongdosa |
—
|
NE NERFINISHED |
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: Tongdosa | Statement: [Haeinsa, otherThreeJewelTemples, Tongdosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherThreeJewelTemples Context triple: [Haeinsa, otherThreeJewelTemples, Tongdosa]
-
A.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
hillTemple
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
C.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
D.
pilgrimageTempleCount
Indicates the number of temples associated with or visited during a particular pilgrimage.
-
E.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
- F. None of above. chosen
Provenance (4 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 6:24 a.m.