Triple
T20476916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ungjin |
E502339
|
entity |
| Predicate | reasonForCapitalRelocationTo |
P56668
|
FINISHED |
| Object | military pressure from Goguryeo |
—
|
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: military pressure from Goguryeo | Statement: [Ungjin, reasonForCapitalRelocationTo, military pressure from Goguryeo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCapitalRelocationTo Context triple: [Ungjin, reasonForCapitalRelocationTo, military pressure from Goguryeo]
-
A.
causeOfPreviousCapitalAbandonment
chosen
Indicates the reason or factor that led to the abandonment of a former capital city.
-
B.
movedImperialCapitalFrom
Indicates the action of transferring an imperial capital city from one location to another.
-
C.
movedImperialCapitalTo
Indicates that a ruler or governing authority relocated the primary seat of imperial government from one capital city to another.
-
D.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
-
E.
laterSeatOfGovernment
Indicates that the referenced place served as a subsequent seat of government for the same political entity after an earlier one.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6996584648190a1a6dfcb57782b7f |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.