Triple
T6248195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanja |
E139773
|
entity |
| Predicate | usedToDisambiguate |
P64049
|
FINISHED |
| Object | homophones in Korean |
—
|
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: homophones in Korean | Statement: [Hanja, usedToDisambiguate, homophones in Korean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToDisambiguate Context triple: [Hanja, usedToDisambiguate, homophones in Korean]
-
A.
usedToInfer
Indicates that one entity serves as a basis or source from which another entity is logically derived or concluded.
-
B.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedToSelect
chosen
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
-
E.
hasDisambiguationPage
Indicates that there exists a disambiguation page used to distinguish between multiple entities or meanings associated with the same term.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633a9a048190856d5247d3b28a2e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.