Triple
T33744347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EWI |
E864658
|
entity |
| Predicate | associatedWithPowiat |
P206662
|
FINISHED |
| Object | powiat wieluński |
—
|
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: powiat wieluński | Statement: [EWI, associatedWithPowiat, powiat wieluński]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPowiat Context triple: [EWI, associatedWithPowiat, powiat wieluński]
-
A.
associatedVoivodeship
Indicates that one entity is administratively or geographically linked to a specific voivodeship (province-level region).
-
B.
associatedWithVoivodeshipCapital
Indicates a relationship where something is linked or connected to the capital city of a voivodeship (a regional administrative unit).
-
C.
dataPowstania
Indicates the date on which something was created or came into existence.
-
D.
hasGmina
Indicates that an entity is administratively associated with, or belongs to, a specific gmina (a basic local government unit/municipality).
-
E.
associatedWithCountySeat
Indicates that an entity has a relationship or connection to a county’s administrative center or county seat.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.