Triple
T6322403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protectorate of Bohemia and Moravia |
E141773
|
entity |
| Predicate | repressionOf |
P18600
|
FINISHED |
| Object | Czech resistance |
—
|
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: Czech resistance | Statement: [Protectorate of Bohemia and Moravia, repressionOf, Czech resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repressionOf Context triple: [Protectorate of Bohemia and Moravia, repressionOf, Czech resistance]
-
A.
repressedDissent
chosen
Indicates that one party has actively suppressed or stifled opposition, criticism, or disagreement from another party or group.
-
B.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
censorshipReason
Indicates the justification or cause given for why certain content is suppressed, restricted, or removed.
-
D.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
E.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c76dfc8190a1d44fd0c4402a0e |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.