Triple
T16046872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polska Ludowa |
E389243
|
entity |
| Predicate | ważneWydarzenie |
P259
|
FINISHED |
| Object | powstanie Solidarności w 1980 |
—
|
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: powstanie Solidarności w 1980 | Statement: [Polska Ludowa, ważneWydarzenie, powstanie Solidarności w 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ważneWydarzenie Context triple: [Polska Ludowa, ważneWydarzenie, powstanie Solidarności w 1980]
-
A.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
C.
isMajorEventOf
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
-
D.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.