Triple
T21807482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | powstanie Polskiego Państwa Podziemnego |
E538384
|
entity |
| Predicate | poprzedzonePrzez |
P25144
|
FINISHED |
| Object | klęska militarna Polski w 1939 |
—
|
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: klęska militarna Polski w 1939 | Statement: [powstanie Polskiego Państwa Podziemnego, poprzedzonePrzez, klęska militarna Polski w 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poprzedzonePrzez Context triple: [powstanie Polskiego Państwa Podziemnego, poprzedzonePrzez, klęska militarna Polski w 1939]
-
A.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
C.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
D.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
E.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.