Triple
T28599409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genmei |
E723864
|
entity |
| Predicate | successorAsCapital |
P30709
|
FINISHED |
| Object | Nagaoka-kyō (later capital) |
—
|
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: Nagaoka-kyō (later capital) | Statement: [Genmei, successorAsCapital, Nagaoka-kyō (later capital)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsCapital Context triple: [Genmei, successorAsCapital, Nagaoka-kyō (later capital)]
-
A.
succeededAsCapitalBy
chosen
Indicates that one capital city has been replaced by another as the official capital of a political entity.
-
B.
successorStateCapital
Indicates that one state capital city has replaced another as the official capital of the same state or region.
-
C.
countrySuccessor
Indicates that one country is the direct successor state to another, inheriting its sovereignty or international status.
-
D.
successorInCountry
Indicates that one entity takes over a role, position, or function from another entity within the same country.
-
E.
successorAdministrativeCenter
Indicates that one administrative center has replaced another as the official seat of administration for a given jurisdiction or entity.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 4:23 a.m.