Triple
T6563669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 蔚山 |
E153846
|
entity |
| Predicate | 行政区类别 |
P70885
|
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.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
B.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
C.
localGovernmentAreaType
chosen
Indicates the specific classification or category of a local government area within an administrative or governmental hierarchy.
-
D.
regionClassification
Indicates how a given area or location is categorized into a specific region based on defined criteria or boundaries.
-
E.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.