Triple
T6777476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act in Restraint of Appeals |
E155593
|
entity |
| Predicate | inForceAtEnactment |
P43146
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Act in Restraint of Appeals, inForceAtEnactment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inForceAtEnactment Context triple: [Act in Restraint of Appeals, inForceAtEnactment, yes]
-
A.
inForceAfter
Indicates that a condition, rule, or agreement becomes valid or operative only after a specified time, event, or state has occurred.
-
B.
initialEnactment
chosen
Indicates that an action, rule, or condition is being put into effect for the first time, marking its original enactment or coming into force.
-
C.
inForceIn
Indicates that a rule, law, agreement, or condition is currently valid and operative within a specified jurisdiction, context, or time frame.
-
D.
inForceAtTimeOfIssue
Indicates that the relationship or condition was in effect at the specific time when the associated item or agreement was issued.
-
E.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26725208190b64935cfd08b2aff |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.