Triple
T27637887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R.34 |
E696514
|
entity |
| Predicate | hasCongressNumber |
P26352
|
FINISHED |
| Object | 114th Congress |
—
|
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: 114th Congress | Statement: [H.R.34, hasCongressNumber, 114th Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCongressNumber Context triple: [H.R.34, hasCongressNumber, 114th Congress]
-
A.
congressionalNumber
chosen
Indicates the specific numbered session or term of a legislative congress to which an entity is associated.
-
B.
lengthOfCongress
Indicates the duration or number of years that a particular session or term of a congress lasts.
-
C.
congressionalNumberingState
Indicates the state associated with a particular numbering or designation of a congressional body or district.
-
D.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
-
E.
representedInCongressNumber
Indicates that an entity’s representation or service is associated with a specific numbered session of a legislative congress.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: April 27, 2026, 2:24 p.m.