Triple
T31276746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changsha dialect |
E797540
|
entity |
| Predicate | capitalOfRegionLanguage |
P145877
|
FINISHED |
| Object | Changsha is capital of Hunan Province |
—
|
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 is capital of Hunan Province | Statement: [Changsha dialect, capitalOfRegionLanguage, Changsha is capital of Hunan Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfRegionLanguage Context triple: [Changsha dialect, capitalOfRegionLanguage, Changsha is capital of Hunan Province]
-
A.
nationalCapitalInLanguage
Indicates that the name of a national capital is expressed or represented in a specified language.
-
B.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific region.
-
C.
countryCapitalOfRegion
Indicates that a country serves as the capital or primary governing state for a specified region.
-
D.
capitalOfRegionContext
chosen
Indicates that a location serves as the capital city or administrative center within the context of a specific region.
-
E.
capitalLocationRegion
Indicates that a location serves as the capital city or administrative center of a specified region.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 29, 2026, 9:13 p.m.