Triple
T9991387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lý dynasty |
E196893
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Lý |
E727043
|
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: Lý | Statement: [Lý dynasty, shortName, Lý]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lý Context triple: [Lý dynasty, shortName, Lý]
-
A.
Lý
chosen
Lý is the Vietnamese royal dynasty that ruled Đại Việt during the 11th–13th centuries, noted for consolidating the state and fostering Buddhism and culture.
-
B.
Lü
Lü is the personal name of Tang of Shang, the legendary founder and first king of China’s Shang dynasty.
-
C.
Luoyi
Luoyi was an ancient Chinese city that served as a major political and cultural center of the Zhou dynasty.
-
D.
Lai
The Lai are an indigenous ethnic group of the broader Mizo community, primarily inhabiting parts of northeast India and neighboring Myanmar, with their own distinct language and cultural traditions.
-
E.
Lai
Lai is a variant spelling of the Chinese surname Li, commonly found in Chinese-speaking communities and their diasporas.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb95842c8190b8cdce9584f19840 |
completed | April 2, 2026, 1:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d25821dde881909f5d4cc6ad048b01 |
completed | April 5, 2026, 12:40 p.m. |
Created at: March 30, 2026, 8:50 p.m.