Triple
T36800676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 崇文门 |
E909312
|
entity |
| Predicate | 相关区划变迁 |
P117243
|
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.
partOfAdministrativeDivisionReform
chosen
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
B.
territorialChange
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
-
C.
hasHistoricalBoundaryChanges
Indicates that the boundaries of an entity have been altered at some point in its history.
-
D.
hasTerritoryReorganizedInto
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
E.
historicalCountyChange
Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.