Triple
T33836955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 安定门 |
E867258
|
entity |
| Predicate | 位于城区 |
P12103
|
FINISHED |
| Object | 北京市东城区 |
—
|
NE NERFINISHED |
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.
所在都市
Indicates the city in which an entity is located or based.
-
B.
locatedInUrbanizationType
Indicates that one entity is situated within, or belongs to, a specific type or category of urbanized area (e.g., city, suburb, metropolitan zone).
-
C.
locatedInPrefectureLevelCity
Indicates that one entity is geographically situated within the jurisdiction or boundaries of a prefecture-level city.
-
D.
withinUrbanArea
chosen
Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
-
E.
locatedInPlannedCity
Indicates that something is situated within the boundaries of a city that was deliberately designed and planned rather than having developed organically.
- 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.