Triple
T16600289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 84 Stat. 719 |
E403312
|
entity |
| Predicate | statutePage |
P123483
|
FINISHED |
| Object | 719 |
—
|
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: 719 | Statement: [84 Stat. 719, statutePage, 719]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statutePage Context triple: [84 Stat. 719, statutePage, 719]
-
A.
statuteInvolved
Indicates that a particular statute or legal provision is implicated, referenced, or applied in relation to a given case, event, or legal matter.
-
B.
statuteName
Indicates the specific legal statute or act by which something is formally designated, governed, or referenced.
-
C.
hasStatuteLaw
Indicates that a jurisdiction or entity is governed by, or possesses, a body of formal written laws enacted by a legislative authority.
-
D.
statuteInterpreted
Indicates that a legal authority (such as a court or agency) has provided an interpretation or authoritative reading of a particular statute.
-
E.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.