Triple
T26949890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haeinsa |
E678751
|
entity |
| Predicate | TripitakaKoreanaLanguage |
P161995
|
FINISHED |
| Object | Classical Chinese |
—
|
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: Classical Chinese | Statement: [Haeinsa, TripitakaKoreanaLanguage, Classical Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TripitakaKoreanaLanguage Context triple: [Haeinsa, TripitakaKoreanaLanguage, Classical Chinese]
-
A.
hasKoreanVersion
Indicates that something has a corresponding version or counterpart that is in the Korean language.
-
B.
languageOfKoreanName
Indicates that the specified language is the language in which the given Korean name is expressed or written.
-
C.
titleInKorean
Indicates that an entity has a specific title expressed in the Korean language.
-
D.
scriptureTypeTranslated
Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
-
E.
국문명
Indicates the Korean-language name or title assigned to an entity.
- 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_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 6:24 a.m.