Triple
T22832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potsdam Conference |
E453
|
entity |
| Predicate | decidedOn |
P807
|
FINISHED |
| Object | division of Germany into occupation zones |
—
|
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: division of Germany into occupation zones | Statement: [Potsdam Conference, decidedOn, division of Germany into occupation zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidedOn Context triple: [Potsdam Conference, decidedOn, division of Germany into occupation zones]
-
A.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
B.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
C.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
D.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
E.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24654724481909ba14b7f68d2a472 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.