Triple
T26949888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haeinsa |
E678751
|
entity |
| Predicate | JanggyeongPanjeonFunction |
P161368
|
FINISHED |
| Object | depository for Tripitaka Koreana woodblocks |
—
|
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: depository for Tripitaka Koreana woodblocks | Statement: [Haeinsa, JanggyeongPanjeonFunction, depository for Tripitaka Koreana woodblocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JanggyeongPanjeonFunction Context triple: [Haeinsa, JanggyeongPanjeonFunction, depository for Tripitaka Koreana woodblocks]
-
A.
bon-gwan
Indicates a traditional Korean clan-origin relationship, linking a person or family name to the ancestral hometown or region from which that lineage originates.
-
B.
PohangIs
Indicates that something is identified as or classified as being Pohang.
-
C.
usesBonGwanSystem
Indicates that an entity follows or applies the Bon-gwan system for identifying or organizing lineage or family origin.
-
D.
YamayakiIncludes
Indicates that something is part of, or contained within, the Yamayaki event or process.
-
E.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
- 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_69f6208934108190b9ae04c0ed2c4dde |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:24 a.m.