Triple
T27279639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayang Miao Autonomous County |
E688293
|
entity |
| Predicate | provincialCapitalOfProvince |
P3433
|
FINISHED |
| Object | Changsha |
—
|
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: Changsha | Statement: [Mayang Miao Autonomous County, provincialCapitalOfProvince, Changsha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provincialCapitalOfProvince Context triple: [Mayang Miao Autonomous County, provincialCapitalOfProvince, Changsha]
-
A.
provinceCapitalOfProvince
Indicates that one entity is the capital city of a specified province.
-
B.
countryCapitalOfProvince
Indicates that a country serves as the capital or primary administrative center of a specified province.
-
C.
countryCapitalProvince
Indicates that a given province serves as the capital administrative region of a specified country.
-
D.
isProvincialCapital
chosen
Indicates that a location serves as the administrative capital of a province within a country or region.
-
E.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 11:06 a.m.