Triple
T17641081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Min (Chinese surname) |
E429227
|
entity |
| Predicate | hasVariantForm |
P457
|
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: [Min (Chinese surname), hasVariantForm, 閔]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 閔 Context triple: [Min (Chinese surname), hasVariantForm, 閔]
-
A.
閔
chosen
閔 is a Chinese character used as a relatively uncommon surname in Chinese-speaking communities.
-
B.
闵
闵 is a relatively uncommon Chinese surname with historical roots and usage in various Chinese-speaking regions.
-
C.
Mǐn
Mǐn is a Chinese surname, written with the character 闵/閔 and borne by various historical and contemporary Chinese individuals.
-
D.
Ming-min
Ming-min is a given name most notably borne by Peng Ming-min, a prominent Taiwanese democracy activist, scholar, and politician.
-
E.
Gongmin
Gongmin was a 14th-century king of the Korean Goryeo dynasty known for his efforts to reform government corruption and reduce Mongol influence over his kingdom.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de50bf481909e938613b38f0202 |
completed | April 19, 2026, 5:53 a.m. |
Created at: April 10, 2026, 6:02 a.m.