Triple
T1135683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonn |
E23133
|
entity |
| Predicate | isUNCity |
P26429
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bonn, isUNCity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUNCity Context triple: [Bonn, isUNCity, yes]
-
A.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
-
B.
isUrbanCounty
Indicates that a county is classified as urban, typically based on population density, development level, or similar urbanization criteria.
-
C.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
-
D.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
E.
cityOwned
Indicates that something is owned, managed, or under the jurisdiction of a city or municipal government.
- F. None of above. chosen
Provenance (4 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bddfa598819088690e1ab010ba0b |
completed | March 1, 2026, 10:29 p.m. |
Created at: March 1, 2026, 7:44 p.m.