Triple
T25301388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Danzig |
E634351
|
entity |
| Predicate | statusOfDanzigAfter |
P4701
|
FINISHED |
| Object | incorporated into Nazi Germany |
—
|
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: incorporated into Nazi Germany | Statement: [Battle of Danzig, statusOfDanzigAfter, incorporated into Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfDanzigAfter Context triple: [Battle of Danzig, statusOfDanzigAfter, incorporated into Nazi Germany]
-
A.
statusOfDanzigBefore
Indicates the political or legal status that Danzig held prior to a specified reference time or event.
-
B.
statusOfTirpitzAfterOperation
Indicates the condition or state of the Tirpitz following the specified military operation.
-
C.
resultOfTannenbergForGermany
Indicates the outcome or consequence that the Battle of Tannenberg had specifically for Germany.
-
D.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
survivorsAtJutland
Indicates that the entities were survivors of the Battle of Jutland.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 1:24 p.m.