Triple
T26960604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Silla |
E679029
|
entity |
| Predicate | unificationOfMostOfKoreanPeninsula |
P70559
|
FINISHED |
| Object | 668 CE |
—
|
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: 668 CE | Statement: [Kingdom of Silla, unificationOfMostOfKoreanPeninsula, 668 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationOfMostOfKoreanPeninsula Context triple: [Kingdom of Silla, unificationOfMostOfKoreanPeninsula, 668 CE]
-
A.
historicalPeriodOfUnification
chosen
Indicates the historical time span during which separate entities were unified into a single political or organizational whole.
-
B.
confederationOfSouthKorea
Indicates a political or organizational confederation that includes or is formed by South Korea.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
unificationLedTo
Indicates that a process of unifying previously separate entities resulted in or caused a particular outcome or state.
-
E.
mainlandNameAfterUnion
Indicates that the predicate links an entity to the name used for its mainland territory after a political or administrative union has taken place.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:31 a.m.