Triple
T32920673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shijiazhuang municipal government |
E842134
|
entity |
| Predicate | governsTypeOfDivision |
P21121
|
FINISHED |
| Object | district |
—
|
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: district | Statement: [Shijiazhuang municipal government, governsTypeOfDivision, district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTypeOfDivision Context triple: [Shijiazhuang municipal government, governsTypeOfDivision, district]
-
A.
typeOfDivision
Indicates the specific category or kind of division that characterizes how something is separated, organized, or partitioned.
-
B.
censusDivisionType
Indicates the classification of a census division according to its official administrative or statistical type.
-
C.
governsTerritoryType
chosen
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
D.
governingClassification
Indicates the classification system or category framework that determines how an entity is organized, labeled, or regulated.
-
E.
governedType
Indicates that one entity determines, constrains, or regulates the type or classification of another entity.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: May 1, 2026, 1:19 a.m.