Triple
T7724178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma |
E175086
|
entity |
| Predicate | characterUnicodeTraditional |
P63661
|
FINISHED |
| Object | U+99AC |
—
|
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: U+99AC | Statement: [Ma, characterUnicodeTraditional, U+99AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterUnicodeTraditional Context triple: [Ma, characterUnicodeTraditional, U+99AC]
-
A.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
B.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
-
C.
correspondsToChineseCharacter
chosen
Indicates that one entity is the equivalent or representation of a specific Chinese written character.
-
D.
ChinesePinyin
Indicates that one entity is the Chinese pinyin (romanized phonetic transcription) representation of another entity.
-
E.
pairedTraditionalName
Indicates that two entities are associated as a traditional name pair, typically used together or in customary combination within a cultural or naming convention.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.