Triple
T451429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GovInfo.gov |
E7137
|
entity |
| Predicate | includesCollection |
P426
|
FINISHED |
| Object | Congressional bills |
—
|
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: Congressional bills | Statement: [GovInfo.gov, includesCollection, Congressional bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCollection Context triple: [GovInfo.gov, includesCollection, Congressional bills]
-
A.
hasCollection
chosen
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
B.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
C.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
D.
hasCollectionItemBy
Indicates that an entity possesses or includes a specific item as part of its collection, identified or referenced by some key or identifier.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef835ae881908884dcc3a46af951 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede3187c8190a7ced078f0ec3476 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.