Triple
T24046258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Chang-ho |
E595527
|
entity |
| Predicate | spouseNameInKorean |
P154657
|
FINISHED |
| Object | Lee Hye-ryeon |
—
|
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: Lee Hye-ryeon | Statement: [An Chang-ho, spouseNameInKorean, Lee Hye-ryeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseNameInKorean Context triple: [An Chang-ho, spouseNameInKorean, Lee Hye-ryeon]
-
A.
spouseNameInVietnamese
Indicates that the predicate specifies the name of a person's spouse as written or expressed in the Vietnamese language.
-
B.
spouseRealName
Indicates that one person is the legally recognized spouse of another, using the spouse’s real (non-alias) name.
-
C.
spouse name
Indicates that one entity is the legally recognized husband or wife of the other, specifying the partner’s name in a marital relationship.
-
D.
spouseNameInPinyin
Indicates that it specifies the spouse’s name written in Pinyin (the Romanized form of Chinese characters).
-
E.
spouseGivenName
Indicates that the value is the given (first) name of a person's spouse in the relationship.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9ca5a18819086da68b69eed8cc1 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:15 p.m.