Triple
T31276780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changsha dialect |
E797540
|
entity |
| Predicate | centerOfDialectArea |
P171534
|
FINISHED |
| Object | Changsha urban core |
—
|
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 urban core | Statement: [Changsha dialect, centerOfDialectArea, Changsha urban core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfDialectArea Context triple: [Changsha dialect, centerOfDialectArea, Changsha urban core]
-
A.
linguisticArea
Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
-
B.
regionOfDialectContinuum
Indicates that a dialect continuum is associated with, or occurs within, a specific geographic region.
-
C.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
D.
relatedDialectArea
Indicates that one dialect area is geographically, historically, or linguistically connected to another dialect area.
-
E.
centerOfCultFrom
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
- F. None of above. chosen
Provenance (4 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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:13 p.m.