Triple
T22315348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Joseon |
E551625
|
entity |
| Predicate | style |
P87
|
FINISHED |
| Object | Wang |
—
|
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: Wang | Statement: [King of Joseon, style, Wang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wang Context triple: [King of Joseon, style, Wang]
-
A.
Wang
chosen
Wang is a common Chinese surname shared by many notable figures across politics, arts, science, and sports.
-
B.
Wang
Wang is a small municipality in Bavaria, Germany, located within the Freising district.
-
C.
Wangs
Wangs is a village in the municipality of Vilters-Wangs in the canton of St. Gallen, Switzerland, known as a local residential and alpine tourism area.
-
D.
Wang He
Wang He was a military commander of the State of Qin during the Warring States period of ancient China, known for his role in the campaigns surrounding the Battle of Changping.
-
E.
Wang Ben
Wang Ben was a Qin dynasty general, traditionally regarded as the son of the famous general Wang Jian, who played a key role in the Qin unification 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1575287688190aa642bb49b24f5a1 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:42 p.m.