Triple
T2846447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudetenland |
E62994
|
entity |
| Predicate | annexationMethod |
P30956
|
FINISHED |
| Object | international agreement |
—
|
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: international agreement | Statement: [Sudetenland, annexationMethod, international agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexationMethod Context triple: [Sudetenland, annexationMethod, international agreement]
-
A.
annexationPolicy
Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
-
B.
annexationInstrument
chosen
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
-
C.
annexationBasis
Indicates the legal, political, or historical grounds used to justify the annexation of one territory by another.
-
D.
annexationApprovedBy
Indicates that the act of annexation has received formal approval or authorization from a specified party or authority.
-
E.
partialAnnexationBy
Indicates a relationship where one entity has annexed or incorporated only a portion of another entity’s territory, authority, or structure, rather than taking it over in full.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf3d00708190966a477fdd855f23 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.