Triple
T236421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silesia |
E4833
|
entity |
| Predicate | wasAnnexedIn |
P960
|
FINISHED |
| Object | 1742 |
—
|
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: 1742 | Statement: [Silesia, wasAnnexedIn, 1742]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAnnexedIn Context triple: [Silesia, wasAnnexedIn, 1742]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
C.
countryOccupied
Indicates that one country has taken control of and is occupying the territory of another country, typically through military or coercive means.
-
D.
independenceDeclaredFrom
Indicates that one entity has formally declared its independence from another entity, ending or rejecting the latter’s authority or control.
-
E.
annexedBy
chosen
Indicates that one entity has been incorporated into and brought under the control or sovereignty of 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccab7648190be6e4f5febc1e313 |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.