Triple
T22466335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bảo Long |
E555363
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Bảo Long |
—
|
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: Bảo Long | Statement: [Bảo Long, givenName, Bảo Long]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bảo Long Context triple: [Bảo Long, givenName, Bảo Long]
-
A.
Bảo Long
chosen
Bảo Long was the eldest son and crown prince of Vietnam’s last emperor, Bảo Đại, and a claimant to the Nguyễn dynasty’s imperial legacy.
-
B.
Hưng Long
Hưng Long was an era name used during the Trần dynasty in medieval Vietnamese history.
-
C.
Hồng Hà
Hồng Hà is the Vietnamese name for the Red River, a major river in Southeast Asia that flows from China through northern Vietnam into the Gulf of Tonkin.
-
D.
Hưng Thống
Hưng Thống was a historical era name used during the Early Lê dynasty in Vietnam.
-
E.
Việt Hưng
Việt Hưng is an urban ward located in Long Biên District on the eastern side of Hanoi, Vietnam.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b837ec081909c4e44d37e8b2acd |
completed | April 29, 2026, 1:14 a.m. |
Created at: April 16, 2026, 8:48 p.m.