Triple
T28075501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 韓 |
E709528
|
entity |
| Predicate | isTraditionalCharacter |
P35394
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [韓, isTraditionalCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalCharacter Context triple: [韓, isTraditionalCharacter, true]
-
A.
hasTraditionalCharacter
chosen
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
B.
hasTraditionalRegionCharacter
Indicates that an entity possesses a characteristic or feature that is typical of, or traditionally associated with, a specific region.
-
C.
hasTraditionalEnglishCharacter
Indicates that something possesses qualities, features, or style typically associated with traditional English culture or heritage.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 8:48 p.m.