Triple
T10034920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄冈市 |
E204941
|
entity |
| Predicate | 下辖区县级行政单位类型 |
P79356
|
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: [黄冈市, 下辖区县级行政单位类型, 市辖区]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 下辖区县级行政单位类型 Context triple: [黄冈市, 下辖区县级行政单位类型, 市辖区]
-
A.
isCountyLevelUnit
Indicates that an entity functions as an administrative unit at the county level within a governmental or territorial hierarchy.
-
B.
subdivisionOfJurisdiction
Indicates that one jurisdiction is a smaller administrative or territorial unit that forms part of a larger jurisdiction.
-
C.
hasCountyLevelCity
Indicates that an entity (typically a region or province) includes or administers one or more cities that hold county-level administrative status.
-
D.
subdivisionRank
Indicates the hierarchical level or type of administrative or territorial subdivision that an entity occupies within a larger organizational or geographic structure.
-
E.
politicalSubdivisionType
chosen
Indicates the specific category or level of governmental or administrative division that characterizes a political subdivision.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.