Triple
T3392582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I – General Provisions |
E71453
|
entity |
| Predicate | rulingsOnEvidenceAddressedIn |
P41134
|
FINISHED |
| Object | Rule 103 |
—
|
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: Rule 103 | Statement: [Article I – General Provisions, rulingsOnEvidenceAddressedIn, Rule 103]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingsOnEvidenceAddressedIn Context triple: [Article I – General Provisions, rulingsOnEvidenceAddressedIn, Rule 103]
-
A.
legalRulingNature
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
B.
judgmentInvolves
chosen
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
C.
documentsDecisionsOn
Indicates that one entity records, details, or formally captures the decisions made about another entity.
-
D.
influencedCourtDecision
Indicates that one entity had an effect on or contributed to the outcome of a court’s decision regarding another entity or matter.
-
E.
decisionsCitableAs
Indicates that certain decisions can be formally cited as authoritative references or precedents in relevant contexts.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.