Triple
T37646203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Honigfelde |
E937043
|
entity |
| Predicate | maStaropolskąNazwę |
P188559
|
FINISHED |
| Object | Bitwa pod Honigfelde |
—
|
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: Bitwa pod Honigfelde | Statement: [Bitwa pod Honigfelde, maStaropolskąNazwę, Bitwa pod Honigfelde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maStaropolskąNazwę Context triple: [Bitwa pod Honigfelde, maStaropolskąNazwę, Bitwa pod Honigfelde]
-
A.
previousVoivodeshipCapital
Indicates that one entity served as the capital of a voivodeship before another capital or administrative change occurred.
-
B.
maMiejsceW
Indicates that something is located in or takes place within a specified place or context.
-
C.
officialNamePolish
Indicates the official or legally recognized name of an entity as expressed in the Polish language.
-
D.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
-
E.
voivodeshipCapitalSince
Indicates that a location has served as the capital of a voivodeship (an administrative region) starting from a specified point in time.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.