Triple
T30266407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Plains urban agglomeration |
E769659
|
entity |
| Predicate | coreProvince |
P29620
|
FINISHED |
| Object | Henan Province |
—
|
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: Henan Province | Statement: [Central Plains urban agglomeration, coreProvince, Henan Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreProvince Context triple: [Central Plains urban agglomeration, coreProvince, Henan Province]
-
A.
mainProvinces
chosen
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
-
B.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
C.
adminProvince
Indicates that one entity serves as the administrative province or primary provincial jurisdiction for another entity.
-
D.
isProvinceOf
Indicates that one region holds the administrative status of a province within, and is governed as a subnational division of, another political entity.
-
E.
populationProvince
Indicates that a specified population figure is associated with, or belongs to, a particular province.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680ad0a14819093b777ff7fe2eda6 |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:43 p.m.