Triple
T21605336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lý dynasty |
E533155
|
entity |
| Predicate | hasCapitalRelocation |
P25378
|
FINISHED |
| Object | Hoa Lư to Thăng Long |
—
|
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: Hoa Lư to Thăng Long | Statement: [Lý dynasty, hasCapitalRelocation, Hoa Lư to Thăng Long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalRelocation Context triple: [Lý dynasty, hasCapitalRelocation, Hoa Lư to Thăng Long]
-
A.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
-
B.
capitalMovedFrom
chosen
Indicates that a capital city was relocated from one place (the source) to another (the destination).
-
C.
administrativeCenterMovedFrom
Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location to another.
-
D.
laterSeatOfGovernment
Indicates that the referenced place served as a subsequent seat of government for the same political entity after an earlier one.
-
E.
succeededAsCapitalBy
Indicates that one capital city has been replaced by another as the official capital of a political entity.
- F. None of above.
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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e4a8088190bf51ab2af2369762 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.