Triple
T33657803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison administration |
E862268
|
entity |
| Predicate | congressNickname |
P177178
|
FINISHED |
| Object | Billion-Dollar 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: Billion-Dollar Congress | Statement: [Harrison administration, congressNickname, Billion-Dollar Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congressNickname Context triple: [Harrison administration, congressNickname, Billion-Dollar Congress]
-
A.
congressName
Indicates the official name or title assigned to a particular congress or legislative session.
-
B.
nicknameLowerHouse
Indicates that one entity is the commonly used or informal nickname for the lower house of a legislative body.
-
C.
U.S.CongressDesignation
Indicates that an entity has been formally designated, named, or recognized through an official act or resolution of the United States Congress.
-
D.
campaignOfficeNickname
Indicates the informal or colloquial name used to refer to a campaign office.
-
E.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
- F. None of above. chosen
Provenance (4 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:42 a.m.