Triple
T17614424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Żagań |
E429045
|
entity |
| Predicate | hasEventCommemoration |
P27243
|
FINISHED |
| Object | annual Great Escape commemorations |
—
|
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: annual Great Escape commemorations | Statement: [Żagań, hasEventCommemoration, annual Great Escape commemorations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventCommemoration Context triple: [Żagań, hasEventCommemoration, annual Great Escape commemorations]
-
A.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
B.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
-
C.
commemorativeEvent
chosen
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
D.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
-
E.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2fd96481908c9f3b566fca6907 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.