Triple
T15629820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu Ding |
E375780
|
entity |
| Predicate | conductedCampaignsAgainst |
P29870
|
FINISHED |
| Object | Yifang |
E1169289
|
NE 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: Yifang | Statement: [Wu Ding, conductedCampaignsAgainst, Yifang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yifang Context triple: [Wu Ding, conductedCampaignsAgainst, Yifang]
-
A.
Yifang
Yifang is a given name of Chinese origin used for both males and females.
-
B.
Guifang
chosen
Guifang was an ancient tribal or regional group on the northern frontiers of the Shang dynasty, known primarily as a target of King Wu Ding’s military campaigns.
-
C.
Yuzhou
Yuzhou is an old Chinese name historically used for the city now widely known as Chongqing.
-
D.
Dunhua
Dunhua is a county-level city in northeastern China's Jilin Province, known for its location within the Yanbian Korean Autonomous Prefecture and its mix of Han and Korean cultural influences.
-
E.
Guisui
Guisui was the historical name for the city now known as Hohhot, a major urban center in northern China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb536348190b93ed3c178d1ffb8 |
completed | April 16, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff7568028481908caa1e49541bbcf1 |
completed | May 9, 2026, 5:56 p.m. |
Created at: April 10, 2026, 4:14 a.m.