Triple
T34124533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 周平王 |
E875237
|
entity |
| Predicate | 迁都地点 |
P67016
|
FINISHED |
| Object | 洛邑 |
—
|
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: 洛邑 | Statement: [周平王, 迁都地点, 洛邑]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 迁都地点 Context triple: [周平王, 迁都地点, 洛邑]
-
A.
movedImperialCapitalFrom
Indicates the action of transferring an imperial capital city from one location to another.
-
B.
movedImperialCapitalTo
chosen
Indicates that a ruler or governing authority relocated the primary seat of imperial government from one capital city to another.
-
C.
movedToNewCapitalRegion
Indicates that an entity has relocated its capital or primary seat of governance to a different capital region.
-
D.
administrativeCenterMovedFrom
Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.