Triple
T2229102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 83rd United States Congress |
E48722
|
entity |
| Predicate | federalCongressNumber |
P26352
|
FINISHED |
| Object | 83 |
—
|
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: 83 | Statement: [83rd United States Congress, federalCongressNumber, 83]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalCongressNumber Context triple: [83rd United States Congress, federalCongressNumber, 83]
-
A.
congressionalNumber
chosen
Indicates the specific numbered session or term of a legislative congress to which an entity is associated.
-
B.
legislatureNumber
Indicates the specific numbered session or term of a legislative body associated with an entity or event.
-
C.
numberOfRepresentatives
Indicates the quantity of representatives associated with a given entity or unit.
-
D.
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).
-
E.
congressName
Indicates the official name or title assigned to a particular congress or legislative session.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0685b688190857a76c1043f4b92 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.