Triple
T31356124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄石港区 |
E799734
|
entity |
| Predicate | urbanLevel |
P35160
|
FINISHED |
| Object | 地级市市辖主城区 |
—
|
LITERAL FINISHED |
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: 地级市市辖主城区 | Statement: [黄石港区, urbanLevel, 地级市市辖主城区]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanLevel Context triple: [黄石港区, urbanLevel, 地级市市辖主城区]
-
A.
cityLevel
chosen
Indicates the administrative or hierarchical rank of a city within a broader regional or national structure.
-
B.
urbanizationLevel
Indicates the degree to which an area or population is characterized by urban development, infrastructure, and density of human settlement.
-
C.
urbanScale
Indicates the extent or magnitude of development, density, or size at which an area or environment can be characterized as urban.
-
D.
cityTierContext
Indicates the classification of a city into a specific tier or level within a contextual hierarchy (such as economic, demographic, or strategic importance).
-
E.
urbanHierarchy
Indicates a hierarchical relationship among urban areas, such as cities or towns, where one is ranked or positioned above or below another in an urban system.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 9:17 p.m.