Triple
T30264810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeměchy |
E769607
|
entity |
| Predicate | isPopulatedPlaceWithin |
P29004
|
FINISHED |
| Object | Kralupy nad Vltavou |
—
|
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: Kralupy nad Vltavou | Statement: [Zeměchy, isPopulatedPlaceWithin, Kralupy nad Vltavou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopulatedPlaceWithin Context triple: [Zeměchy, isPopulatedPlaceWithin, Kralupy nad Vltavou]
-
A.
isPopulatedPlaceIn
chosen
Indicates that a populated place (such as a city, town, or village) is located within a specified larger geographic or administrative area.
-
B.
isPopulatedPlace
Indicates that the subject is a geographic location where people live or have lived, such as a city, town, village, or settlement.
-
C.
isIncorporatedPlace
Indicates that a location is a legally established, self-governing municipal entity (such as a city, town, or village) recognized as an incorporated place.
-
D.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
-
E.
isInlandSettlement
Indicates that a settlement is located away from the coast, without direct access to the sea or ocean.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680abfd708190ba353bf8c06d794a |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:42 p.m.