Triple
T21807366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Rzesza |
E538382
|
entity |
| Predicate | dataPowstania |
P145721
|
FINISHED |
| Object | 1933-01-30 |
—
|
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: 1933-01-30 | Statement: [III Rzesza, dataPowstania, 1933-01-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPowstania Context triple: [III Rzesza, dataPowstania, 1933-01-30]
-
A.
associatedVoivodeship
Indicates that one entity is administratively or geographically linked to a specific voivodeship (province-level region).
-
B.
numberOfGminas
Indicates the total count of gminas (municipal administrative units) associated with a given entity.
-
C.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
-
D.
associatedWithVoivodeshipCapital
Indicates a relationship where something is linked or connected to the capital city of a voivodeship (a regional administrative unit).
-
E.
containsVoivodeship
Indicates that one administrative region or entity geographically includes or encompasses a voivodeship within its boundaries.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.