Triple
T2243275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Prussia |
E49443
|
entity |
| Predicate | wasSubjectTo |
P1313
|
FINISHED |
| Object | Allied occupation after World War II |
—
|
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: Allied occupation after World War II | Statement: [East Prussia, wasSubjectTo, Allied occupation after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSubjectTo Context triple: [East Prussia, wasSubjectTo, Allied occupation after World War II]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
D.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
-
E.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0c157e88190a5bc876d9591a24b |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.