Triple
T26949889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haeinsa |
E678751
|
entity |
| Predicate | TripitakaKoreanaMaterial |
P50559
|
FINISHED |
| Object | wooden printing blocks |
—
|
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: wooden printing blocks | Statement: [Haeinsa, TripitakaKoreanaMaterial, wooden printing blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TripitakaKoreanaMaterial Context triple: [Haeinsa, TripitakaKoreanaMaterial, wooden printing blocks]
-
A.
placeOfManuscriptTradition
Indicates the location where a manuscript tradition is preserved, transmitted, or primarily associated.
-
B.
traditionalMaterial
chosen
Indicates that something is made from, incorporates, or is characterized by materials associated with long-established or customary practices.
-
C.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
-
D.
thematicMaterial
Indicates that one entity serves as the primary recurring idea, motif, or thematic content that is developed or referenced by another entity.
-
E.
materialInLore
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
- 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_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. |
Created at: April 27, 2026, 6:24 a.m.