Triple
T17532436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Zhou |
E426969
|
entity |
| Predicate | yearOfConquestOfNorthernQi |
P3478
|
FINISHED |
| Object | 577 |
—
|
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: 577 | Statement: [Northern Zhou, yearOfConquestOfNorthernQi, 577]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfConquestOfNorthernQi Context triple: [Northern Zhou, yearOfConquestOfNorthernQi, 577]
-
A.
conquestYear
chosen
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
C.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
D.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
E.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e453695734819092d4dcbab4a4fa01 |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.