Triple
T34262535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SJ |
E879073
|
entity |
| Predicate | isReusedInOtherPolishRegions |
P91997
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [SJ, isReusedInOtherPolishRegions, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReusedInOtherPolishRegions Context triple: [SJ, isReusedInOtherPolishRegions, false]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
associatedVoivodeship
Indicates that one entity is administratively or geographically linked to a specific voivodeship (province-level region).
-
C.
containsVoivodeship
Indicates that one administrative region or entity geographically includes or encompasses a voivodeship within its boundaries.
-
D.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
-
E.
countryDuringPolishLithuanianCommonwealth
Indicates that a country existed within or was part of the Polish–Lithuanian Commonwealth 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.