Triple
T2014853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichstag Fire Decree |
E43770
|
entity |
| Predicate | suspendedRight |
P6070
|
FINISHED |
| Object | freedom of expression |
—
|
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: freedom of expression | Statement: [Reichstag Fire Decree, suspendedRight, freedom of expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspendedRight Context triple: [Reichstag Fire Decree, suspendedRight, freedom of expression]
-
A.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
B.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
C.
suspension
chosen
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
D.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b610a88190bc10fd7dda19da08 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.