Triple
T14933867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olsztyn |
E372338
|
entity |
| Predicate | currentVoivodeshipCapitalSince |
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: [Olsztyn, currentVoivodeshipCapitalSince, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVoivodeshipCapitalSince Context triple: [Olsztyn, currentVoivodeshipCapitalSince, 1999]
-
A.
voivodeshipCapitalSince
chosen
Indicates that a location has served as the capital of a voivodeship (an administrative region) starting from a specified point in time.
-
B.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
-
C.
historicalCapitalNow
Indicates that a location currently serves as the capital of an entity for which it also held capital status at some point in the past.
-
D.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
E.
regionCapitalSince
Indicates that one region has served as the capital of another region continuously since 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded646a0808190ba5c0c91bde011c5 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.