Triple
T9707788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 48 |
E234942
|
entity |
| Predicate | repealedWith |
P61087
|
FINISHED |
| Object | end of the Weimar Constitution |
—
|
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: end of the Weimar Constitution | Statement: [Article 48, repealedWith, end of the Weimar Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repealedWith Context triple: [Article 48, repealedWith, end of the Weimar Constitution]
-
A.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
B.
repealedUnder
Indicates that one legal rule, law, or regulation has been formally revoked or annulled by virtue of another specified legal authority or provision.
-
C.
repealedProvisionOf
Indicates that one legal provision has been formally revoked, annulled, or rendered no longer in force by another provision or act.
-
D.
repealMentionedIn
Indicates that a repeal action or event is referenced or discussed within a particular document, statement, or context.
-
E.
repealedAfterEvent
chosen
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da5e09081909456909d768611e6 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.