Triple
T26933535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cultural Heritage Protection Act of South Korea |
E678299
|
entity |
| Predicate | shortTitleInKorean |
P6037
|
FINISHED |
| Object | 문화재보호법 |
—
|
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: 문화재보호법 | Statement: [Cultural Heritage Protection Act of South Korea, shortTitleInKorean, 문화재보호법]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortTitleInKorean Context triple: [Cultural Heritage Protection Act of South Korea, shortTitleInKorean, 문화재보호법]
-
A.
shortNameInJapanese
Indicates that an entity has a specific abbreviated or shorter form of its name expressed in the Japanese language.
-
B.
titleInKorean
Indicates that an entity has a specific title expressed in the Korean language.
-
C.
equivalentTitleInKorean
Indicates that one title has an equivalent or corresponding title expressed in the Korean language.
-
D.
hasShortTitle
chosen
Indicates that an entity is associated with a brief or abbreviated title.
-
E.
nameInKorean
Indicates that an entity’s name is expressed in the Korean language.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:14 a.m.