Triple
T5478001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restricted Data |
E123401
|
entity |
| Predicate | legalDefinitionLocatedIn |
P23668
|
FINISHED |
| Object | 42 U.S.C. § 2014(y) |
—
|
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: 42 U.S.C. § 2014(y) | Statement: [Restricted Data, legalDefinitionLocatedIn, 42 U.S.C. § 2014(y)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDefinitionLocatedIn Context triple: [Restricted Data, legalDefinitionLocatedIn, 42 U.S.C. § 2014(y)]
-
A.
legalDefinitionJurisdiction
Indicates the jurisdiction or authority under which a particular legal definition is established or applies.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
-
D.
legalDefinitionSource
chosen
Indicates the source (such as a statute, regulation, or case) from which a particular legal definition is derived.
-
E.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd92460f008190bf9d64ddd9c507a7 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.