Triple
T26306794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiangdong |
E661706
|
entity |
| Predicate | capitalCityDuringEasternWu |
P134108
|
FINISHED |
| Object | Jianye |
—
|
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: Jianye | Statement: [Jiangdong, capitalCityDuringEasternWu, Jianye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityDuringEasternWu Context triple: [Jiangdong, capitalCityDuringEasternWu, Jianye]
-
A.
successorCapitalOfNorthernWei
Indicates that one city served as the capital that succeeded a previous capital of the Northern Wei dynasty.
-
B.
capitalInChinese
Indicates that one entity is the name of a capital city expressed in the Chinese language for the other entity.
-
C.
capitalCityDuringEra
chosen
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
-
D.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
E.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 26, 2026, 10:19 p.m.