Triple
T32458429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuhua County, Guangdong |
E829495
|
entity |
| Predicate | hasPrefectureLevelCitySeat |
P28963
|
FINISHED |
| Object | Meizhou |
—
|
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: Meizhou | Statement: [Wuhua County, Guangdong, hasPrefectureLevelCitySeat, Meizhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrefectureLevelCitySeat Context triple: [Wuhua County, Guangdong, hasPrefectureLevelCitySeat, Meizhou]
-
A.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
-
B.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
C.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
D.
isPrefecturalCityOf
chosen
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
E.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 1, 2026, 12:56 a.m.