Triple
T30443873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bạch Đằng (1288) |
E774523
|
entity |
| Predicate | TrầnHưngĐạoRole |
P169444
|
FINISHED |
| Object | overall commander of Đại Việt forces |
—
|
LITERAL 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: overall commander of Đại Việt forces | Statement: [Battle of Bạch Đằng (1288), TrầnHưngĐạoRole, overall commander of Đại Việt forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TrầnHưngĐạoRole Context triple: [Battle of Bạch Đằng (1288), TrầnHưngĐạoRole, overall commander of Đại Việt forces]
-
A.
ChineseCommander
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
-
B.
Hen WenRole
Indicates that the entity has the role or function associated with a hen.
-
C.
BaekjeCommander
Indicates that one entity serves as a military commander or leader associated with the Baekje kingdom.
-
D.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
E.
emperorRole
Indicates that an entity holds or fulfills the role, position, or office of an emperor in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6869c15d48190be8870c750df12ed |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:08 p.m.