Triple
T28798062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulm postal region |
E727142
|
entity |
| Predicate | hasCenterCity |
P2106
|
FINISHED |
| Object | Ulm |
—
|
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: Ulm | Statement: [Ulm postal region, hasCenterCity, Ulm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCenterCity Context triple: [Ulm postal region, hasCenterCity, Ulm]
-
A.
hasCentralCities
Indicates that an entity is associated with one or more cities that serve as its primary or central urban locations.
-
B.
hasPopulationCenter
chosen
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
C.
servesAsFocusCityFor
Indicates that a city functions as a primary or designated focus city for an airline, organization, or transportation network, typically hosting significant but not hub-level operations or activities.
-
D.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
E.
hasDemographicCenter
Indicates that an entity has a primary geographic location where the majority or core concentration of its associated population or demographic group is found.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 6:26 a.m.