Triple
T1567811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 103-141 |
E33470
|
entity |
| Predicate | introducedInCongress |
P26352
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Public Law 103-141, introducedInCongress, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInCongress Context triple: [Public Law 103-141, introducedInCongress, 1993]
-
A.
introducedInLegislatureBy
Indicates that a piece of legislation was formally presented or sponsored in a legislative body by a specific legislator or legislative entity.
-
B.
congressionalNumber
chosen
Indicates the specific numbered session or term of a legislative congress to which an entity is associated.
-
C.
representedInCongressBy
Indicates that one entity serves as the official congressional representative (e.g., legislator) for another entity (such as a person, group, or geographic area).
-
D.
sponsoredInSenateBy
Indicates that a legislative measure or proposal was formally introduced or championed in the Senate by a specific senator.
-
E.
legislatureAffected
Indicates that an action, event, or measure has an impact on a legislative body or its functioning.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.