Triple
T1156338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowy Sącz |
E23790
|
entity |
| Predicate | timePeriodAsVoivodeshipCapital |
P20655
|
FINISHED |
| Object | 1975–1998 |
—
|
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: 1975–1998 | Statement: [Nowy Sącz, timePeriodAsVoivodeshipCapital, 1975–1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsVoivodeshipCapital Context triple: [Nowy Sącz, timePeriodAsVoivodeshipCapital, 1975–1998]
-
A.
timeAsCapital
chosen
Indicates the period during which a particular city served as the capital of a political entity.
-
B.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
-
C.
timeInCapital
Indicates that a specified amount of time is spent or occurs within the capital city of a given political or administrative entity.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
servedAsNationalCapitalFrom
Indicates that a place functioned as the national capital of a country or political entity during a specified time period.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc912300819084c9c69783055a70 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.