Triple
T30829169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长乐路 |
E785161
|
entity |
| Predicate | 城市功能区类型 |
P31474
|
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.
urbanDistrictType
chosen
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
B.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
C.
行政区
Indicates a relationship where one entity is an administrative division or jurisdictional area associated with, governed by, or belonging to another entity.
-
D.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
E.
相关城市群
Indicates a relationship where an entity is associated with, belongs to, or is relevant to a particular urban agglomeration or city cluster.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690f8eed08190ae78208498b04506 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.