Triple
T35188482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (territorial jurisdiction) |
E1016052
|
entity |
| Predicate | scopeClarifiedBy |
P13667
|
FINISHED |
| Object | federal jurisdictional statutes |
—
|
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: federal jurisdictional statutes | Statement: [United States (territorial jurisdiction), scopeClarifiedBy, federal jurisdictional statutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeClarifiedBy Context triple: [United States (territorial jurisdiction), scopeClarifiedBy, federal jurisdictional statutes]
-
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.
scopeDetail
Indicates a more specific or refined characterization of the extent, boundaries, or coverage of something within a broader scope.
-
C.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
scopeClaim
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
E.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.