Triple
T27029542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hwaeom |
E680880
|
entity |
| Predicate | founderInKorea |
P178273
|
FINISHED |
| Object | Uisang |
—
|
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: Uisang | Statement: [Hwaeom, founderInKorea, Uisang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderInKorea Context triple: [Hwaeom, founderInKorea, Uisang]
-
A.
founderInJapan
Indicates that an entity is the founder of something (such as an organization or company) specifically in Japan.
-
B.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
-
C.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
D.
founderNationality
Indicates that the specified person’s country of origin or citizenship is the one associated with the founder in question.
-
E.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 27, 2026, 7:13 a.m.