Triple
T2837811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich Betrayal |
E62391
|
entity |
| Predicate | framesAs |
P42942
|
FINISHED |
| Object | abandonment of Czechoslovak sovereignty |
—
|
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: abandonment of Czechoslovak sovereignty | Statement: [Munich Betrayal, framesAs, abandonment of Czechoslovak sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: framesAs Context triple: [Munich Betrayal, framesAs, abandonment of Czechoslovak sovereignty]
-
A.
frameType
Indicates the specific structural or categorical kind of frame associated with an entity or relation.
-
B.
frameSize
Indicates the size or dimensions of a frame associated with an entity.
-
C.
frameDevice
Indicates that one entity serves as a structural or supporting frame for another device or object.
-
D.
framedBy
Indicates that one entity serves as a surrounding boundary or enclosing structure that visually or conceptually frames another entity.
-
E.
frameDependent
Indicates that the truth or interpretation of the relationship depends on the particular reference frame, context, or perspective from which it is evaluated.
- F. None of above. chosen
Provenance (4 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdeede0488190a9782f55b57559ee |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.