Triple
T27848142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuangyin |
E703879
|
entity |
| Predicate | regionReunified |
P170277
|
FINISHED |
| Object | most of northern China |
—
|
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: most of northern China | Statement: [Kuangyin, regionReunified, most of northern China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionReunified Context triple: [Kuangyin, regionReunified, most of northern China]
-
A.
reunifiedAs
Indicates that entities which were previously separated or divided have been brought back together into a single unified whole.
-
B.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
-
C.
consolidatedRegion
chosen
Indicates that multiple smaller regions have been merged or unified into a single, larger region.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 6:08 p.m.