Triple
T26574819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don’t Ask, Don’t Tell Repeal Act of 2010 |
E666919
|
entity |
| Predicate | relatedBill |
P143942
|
FINISHED |
| Object | S. 4023 |
—
|
NE NERFINISHED |
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: S. 4023 | Statement: [Don’t Ask, Don’t Tell Repeal Act of 2010, relatedBill, S. 4023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedBill Context triple: [Don’t Ask, Don’t Tell Repeal Act of 2010, relatedBill, S. 4023]
-
A.
relationshipWithBill
chosen
Indicates that there exists some specified type of relationship or association between an entity and Bill.
-
B.
billedThrough
Indicates that one party’s billing or payment is processed via, or routed through, another party or system.
-
C.
financialBillsGovernedBy
Indicates that certain financial bills or obligations are regulated, controlled, or overseen by a specified governing authority or entity.
-
D.
billingEntity
Indicates the entity that is responsible for issuing or receiving bills or invoices in a transaction or service relationship.
-
E.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 27, 2026, 1:59 a.m.