Triple
T3392580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I – General Provisions |
E71453
|
entity |
| Predicate | scopeDefinedIn |
P13667
|
FINISHED |
| Object | Rule 101 |
—
|
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 101 | Statement: [Article I – General Provisions, scopeDefinedIn, Rule 101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeDefinedIn Context triple: [Article I – General Provisions, scopeDefinedIn, Rule 101]
-
A.
scopeDefinedBy
chosen
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
B.
scopeOfDeclaration
Indicates the syntactic region or context within which a particular declaration is valid and can be referenced.
-
C.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
- 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.