Triple
T28607627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longyang District |
E724094
|
entity |
| Predicate | parentPrefectureLevelCity |
P28963
|
FINISHED |
| Object | Baoshan City |
—
|
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: Baoshan City | Statement: [Longyang District, parentPrefectureLevelCity, Baoshan City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentPrefectureLevelCity Context triple: [Longyang District, parentPrefectureLevelCity, Baoshan City]
-
A.
prefecture-levelCity
Indicates that one entity is a city that holds prefecture-level administrative status in relation to another entity (typically a higher-level region or governing structure).
-
B.
isPrefecturalCityOf
chosen
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
C.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
D.
hostPrefecture
Indicates the prefecture that serves as the host location for an event, activity, or entity.
-
E.
homePrefecture
Indicates the prefecture that an entity considers its home or place of origin.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 4:28 a.m.