Triple
T37646221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa pod Honigfelde |
E937043
|
entity |
| Predicate | miejsceWydarzeniaHistorycznego |
P127335
|
FINISHED |
| Object | Mewe |
—
|
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: Mewe | Statement: [Bitwa pod Honigfelde, miejsceWydarzeniaHistorycznego, Mewe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miejsceWydarzeniaHistorycznego Context triple: [Bitwa pod Honigfelde, miejsceWydarzeniaHistorycznego, Mewe]
-
A.
significantEventPlace
chosen
Indicates the place where a significant event occurred or is associated with an entity.
-
B.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
C.
placeOfEventCommemorated
Indicates the location where the event being commemorated actually took place.
-
D.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
E.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.