Triple
T5678436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 79-585 |
E125141
|
entity |
| Predicate | typeOfEnactment |
P2588
|
FINISHED |
| Object | public act |
—
|
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: public act | Statement: [Public Law 79-585, typeOfEnactment, public act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEnactment Context triple: [Public Law 79-585, typeOfEnactment, public act]
-
A.
enactedWith
Indicates that an action, law, or policy was formally established or brought into effect through the involvement or authority of a specified agent or instrument.
-
B.
enactedAs
Indicates that one entity has been formally established, implemented, or made legally effective in the specific form represented by another entity.
-
C.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
initialEnactment
Indicates that an action, rule, or condition is being put into effect for the first time, marking its original enactment or coming into force.
-
E.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.