Triple
T20330982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krotoszyn |
E492478
|
entity |
| Predicate | hasVoivodeshipCapitalNearby |
P41518
|
FINISHED |
| Object | Poznań |
—
|
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: Poznań | Statement: [Krotoszyn, hasVoivodeshipCapitalNearby, Poznań]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoivodeshipCapitalNearby Context triple: [Krotoszyn, hasVoivodeshipCapitalNearby, Poznań]
-
A.
associatedWithVoivodeshipCapital
Indicates a relationship where something is linked or connected to the capital city of a voivodeship (a regional administrative unit).
-
B.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
-
C.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
D.
regionCapitalNearby
chosen
Indicates that a capital city of a region is located close to the referenced place or entity.
-
E.
voivodeshipCapitalSince
Indicates that a location has served as the capital of a voivodeship (an administrative region) starting from a specified point in time.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e7baf481909282293d78597634 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:22 a.m.