Triple
T28389435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 朝天门 |
E719108
|
entity |
| Predicate | 行政区划 |
P44156
|
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.
行政区
Indicates a relationship where one entity is an administrative division or jurisdictional area associated with, governed by, or belonging to another entity.
-
B.
郡
Indicates that the subject municipality is administratively located within the specified district.
-
C.
administrativeDistricts
chosen
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
D.
administrativeOkrug
Indicates that one entity functions as an administrative district or okrug governing or encompassing another entity within an administrative hierarchy.
-
E.
rankInChineseAdministrativeHierarchy
Indicates the relative level or position an administrative unit holds within the formal hierarchy of Chinese government administration.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64ceb933081909992f16507b0e667 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:12 a.m.