Triple
T26452730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đinh dynasty |
E665396
|
entity |
| Predicate | centralPowerBase |
P112282
|
FINISHED |
| Object | Hoa Lư Citadel |
—
|
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: Hoa Lư Citadel | Statement: [Đinh dynasty, centralPowerBase, Hoa Lư Citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPowerBase Context triple: [Đinh dynasty, centralPowerBase, Hoa Lư Citadel]
-
A.
mainCentralPower
Indicates that an entity functions as the primary central authority or dominant power within a given system or context.
-
B.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
C.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
D.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
E.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 12:06 a.m.