Triple
T10110042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Xiang |
E218215
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Loudi |
E175006
|
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: Loudi | Statement: [Old Xiang, spokenIn, Loudi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loudi Context triple: [Old Xiang, spokenIn, Loudi]
-
A.
Loudi
chosen
Loudi is a prefecture-level city in south-central China known for its role as an industrial and transportation hub within Hunan Province.
-
B.
Changde
Changde is a city in northwestern Hunan Province, China, historically significant as a major battleground during the Second Sino-Japanese War.
-
C.
Yiyang
Yiyang is a prefecture-level city in south-central China known for its location along the Zi River and its role as an important regional center in Hunan Province.
-
D.
Shaoyang
Shaoyang is a prefecture-level city in south-central China known for its long history, cultural heritage, and location in the southwestern part of Hunan Province.
-
E.
Hengyang
Hengyang is a major industrial and transportation hub city in southern China, located along the Xiang River in the south of Hunan Province.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cdb3c88190a74f75bf865664f3 |
completed | April 2, 2026, 2:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d74fc3f9608190b4472b2b87009cca |
completed | April 9, 2026, 7:05 a.m. |
Created at: March 30, 2026, 9:03 p.m.