Triple
T19217365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuo |
E480521
|
entity |
| Predicate | romanizationOf |
P2508
|
FINISHED |
| Object | 郭 |
—
|
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: 郭 | Statement: [Kuo, romanizationOf, 郭]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 郭 Context triple: [Kuo, romanizationOf, 郭]
-
A.
郭
chosen
郭 is a common Chinese surname borne by numerous individuals across the Chinese-speaking world.
-
B.
朱
朱 is a common Chinese surname with historical roots and notable bearers across Chinese-speaking communities.
-
C.
鄭
鄭 is a common Korean family name of Chinese origin, typically romanized as Jeong, Jung, or Chung.
-
D.
陳
陳 is a common Chinese surname and character with historical roots, widely used across Chinese-speaking communities and often romanized as "Chan," "Chen," or similar variants.
-
E.
胡
胡 is a common Chinese character used both as a surname and in various words, often historically associated with non-Han peoples or regions to the north and west of China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3aff9c8190974363683b8246f5 |
completed | April 20, 2026, 10:04 a.m. |
Created at: April 10, 2026, 1:23 p.m.