Triple
T12707835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yingkou |
E303634
|
entity |
| Predicate | isPrefectureLevelCity |
P96684
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yingkou, isPrefectureLevelCity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrefectureLevelCity Context triple: [Yingkou, isPrefectureLevelCity, true]
-
A.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
B.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
C.
prefecture-levelCity
chosen
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).
-
D.
locatedInPrefectureLevelCity
Indicates that one entity is geographically situated within the jurisdiction or boundaries of a prefecture-level city.
-
E.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620663e881908d367170ed6d2c81 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.