Triple
T722454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obrona Helu |
E14646
|
entity |
| Predicate | before |
P97
|
FINISHED |
| Object | German consolidation of control over Polish Baltic coast |
—
|
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: German consolidation of control over Polish Baltic coast | Statement: [Obrona Helu, before, German consolidation of control over Polish Baltic coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: before Context triple: [Obrona Helu, before, German consolidation of control over Polish Baltic coast]
-
A.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
B.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
C.
precondition
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
D.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
E.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a591124c8190842e7ef18b064198 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.