Triple
T33836974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 安定门 |
E867258
|
entity |
| Predicate | 相关行政区划 |
P158179
|
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.
行政区
chosen
Indicates a relationship where one entity is an administrative division or jurisdictional area associated with, governed by, or belonging to another entity.
-
B.
相关城市群
Indicates a relationship where an entity is associated with, belongs to, or is relevant to a particular urban agglomeration or city cluster.
-
C.
所属地区教育系统
Indicates that an entity belongs to, is governed by, or is managed under a particular regional education system or educational administrative jurisdiction.
-
D.
関与地域
Indicates a geographical area or region that is involved in, affected by, or relevant to a particular activity, event, or relationship.
-
E.
包含自治体
Indicates that one administrative body geographically or jurisdictionally includes another subordinate municipality within its boundaries.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002f38308190af948b97a35a5b09 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.