Triple
T7399633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lê Hoàn |
E170711
|
entity |
| Predicate | eraNameUsed |
P2938
|
FINISHED |
| Object | Ứng Thiên |
E647399
|
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: Ứng Thiên | Statement: [Lê Hoàn, eraNameUsed, Ứng Thiên]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ứng Thiên Context triple: [Lê Hoàn, eraNameUsed, Ứng Thiên]
-
A.
Ứng Thiên
chosen
Ứng Thiên was an imperial era name used during the Early Lê dynasty in Vietnamese history.
-
B.
Longcheng
Longcheng was the principal royal city and political center of the Xiongnu confederation in ancient Inner Asia.
-
C.
Guandu
Guandu is a district in northern Taipei, Taiwan, known for its riverside wetlands, hot springs, and the historic Guandu Temple.
-
D.
Zhizhong
Zhizhong is a Chinese given name shared by various individuals, including historical and contemporary figures.
-
E.
Lüshun
Lüshun is a strategically important port city in northeastern China, historically known as Port Arthur and noted for its role in several major conflicts.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24dbf288190b8dfea455148841b |
completed | March 27, 2026, 9:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8110b6ffc819080f65c590f6ac156 |
completed | March 28, 2026, 5:34 p.m. |
Created at: March 27, 2026, 3:10 p.m.