Triple
T6084687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hangul Jamo Extended-A |
E135607
|
entity |
| Predicate | containsCharactersUsedIn |
P64709
|
FINISHED |
| Object | historical Korean texts |
—
|
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: historical Korean texts | Statement: [Hangul Jamo Extended-A, containsCharactersUsedIn, historical Korean texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCharactersUsedIn Context triple: [Hangul Jamo Extended-A, containsCharactersUsedIn, historical Korean texts]
-
A.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
B.
containsAssignedCharacters
Indicates that an entity includes or holds one or more characters that have been specifically assigned to it.
-
C.
hasSpecialCharacter
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
D.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
E.
characterCoverage
chosen
Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057891dc88190997c4e32b2261fb3 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.