Triple
T4358559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 61st United States Congress |
E98609
|
entity |
| Predicate | legislativeOutputType |
P2588
|
FINISHED |
| Object | federal 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 statutes | Statement: [61st United States Congress, legislativeOutputType, federal statutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeOutputType Context triple: [61st United States Congress, legislativeOutputType, federal statutes]
-
A.
legislativeOutput
Indicates the amount or nature of laws, regulations, or formal decisions produced by a legislative body.
-
B.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
C.
legislativeOutcome
Indicates the result or final status of a legislative process, such as whether a proposed law or measure was passed, rejected, amended, or otherwise resolved.
-
D.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
E.
legislativeArticle
Indicates a relationship where one entity is a specific article or clause within a legislative or legal document that governs or regulates another entity.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c7fa1881908bdc844a7142eb65 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.