Triple
T1299109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szczecin |
E27720
|
entity |
| Predicate | voivodeshipCapitalSince |
P28406
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Szczecin, voivodeshipCapitalSince, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voivodeshipCapitalSince Context triple: [Szczecin, voivodeshipCapitalSince, 1999]
-
A.
previousVoivodeship
Indicates that one voivodeship was the immediately preceding administrative region for another in a temporal or historical sequence.
-
B.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
C.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
-
D.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
E.
municipalitySeat
Indicates that one entity serves as the administrative center or capital (seat) of a municipality.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c3b9ebdc819098de4d3288201bc1 |
completed | March 1, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.