Triple
T30285223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cegielski factory complex in Poznań |
E770215
|
entity |
| Predicate | workersParticipatedIn |
P74692
|
FINISHED |
| Object | 1956 Poznań uprising |
—
|
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: 1956 Poznań uprising | Statement: [Cegielski factory complex in Poznań, workersParticipatedIn, 1956 Poznań uprising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workersParticipatedIn Context triple: [Cegielski factory complex in Poznań, workersParticipatedIn, 1956 Poznań uprising]
-
A.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
B.
hasBeenInvolvedIn
chosen
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
C.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6810831388190a9522031b2271680 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:46 p.m.