Triple
T20023599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Tucker Act |
E494920
|
entity |
| Predicate | TuckerActCodifiedAt |
P138407
|
FINISHED |
| Object | 28 U.S.C. § 1491 |
—
|
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: 28 U.S.C. § 1491 | Statement: [Little Tucker Act, TuckerActCodifiedAt, 28 U.S.C. § 1491]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TuckerActCodifiedAt Context triple: [Little Tucker Act, TuckerActCodifiedAt, 28 U.S.C. § 1491]
-
A.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
B.
dateSignedIntoLaw
Indicates the date on which a law or legal measure was formally approved and enacted into law.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
legislatedUnder
Indicates that a law, regulation, or policy was created, enacted, or established according to the authority, framework, or provisions of a specific higher-level law or legal regime.
-
E.
timePeriodOfCodification
Indicates the time period during which something was formally codified or set into an official, systematic form.
- F. None of above. chosen
Provenance (4 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:35 p.m.