Triple
T30783587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seeburg |
E783891
|
entity |
| Predicate | locatedInVoivodeshipNow |
P84126
|
FINISHED |
| Object | Warmian-Masurian Voivodeship |
—
|
NE NERFINISHED |
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: Warmian-Masurian Voivodeship | Statement: [Seeburg, locatedInVoivodeshipNow, Warmian-Masurian Voivodeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInVoivodeshipNow Context triple: [Seeburg, locatedInVoivodeshipNow, Warmian-Masurian Voivodeship]
-
A.
associatedVoivodeship
chosen
Indicates that one entity is administratively or geographically linked to a specific voivodeship (province-level region).
-
B.
containsVoivodeship
Indicates that one administrative region or entity geographically includes or encompasses a voivodeship within its boundaries.
-
C.
associatedWithVoivodeshipCapital
Indicates a relationship where something is linked or connected to the capital city of a voivodeship (a regional administrative unit).
-
D.
dataPowstania
Indicates the date on which something was created or came into existence.
-
E.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: April 29, 2026, 8:41 p.m.