Triple
T4200266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 41(b) |
E86047
|
entity |
| Predicate | defaultEffect |
P1634
|
FINISHED |
| Object | adjudication on the merits |
—
|
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: adjudication on the merits | Statement: [Rule 41(b), defaultEffect, adjudication on the merits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultEffect Context triple: [Rule 41(b), defaultEffect, adjudication on the merits]
-
A.
visualEffect
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
B.
primaryEffect
chosen
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
C.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
D.
defaultOn
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
E.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0363bbb8819093f396afe91972e2 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.