Triple
T25875931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Qin |
E651900
|
entity |
| Predicate | capitalDuringReignOfYaoXing |
P9119
|
FINISHED |
| Object | Chang'an |
—
|
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: Chang'an | Statement: [Later Qin, capitalDuringReignOfYaoXing, Chang'an]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalDuringReignOfYaoXing Context triple: [Later Qin, capitalDuringReignOfYaoXing, Chang'an]
-
A.
producedRulingDynastyOf
Indicates that one entity (such as a region, people, or prior polity) gave rise to or was the origin context for a particular ruling dynasty.
-
B.
capitalDuringReign
chosen
Indicates that a particular city or location served as the capital of a political entity during the reign of a specified ruler.
-
C.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
D.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
E.
recognizedRulingDynasty
Indicates that an authority or group formally acknowledges a particular ruling dynasty as legitimate or in power.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 22, 2026, 8:12 a.m.