Triple
T31757393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democrats approached filibuster-proof majority |
E810588
|
entity |
| Predicate | thresholdMentioned |
P172273
|
FINISHED |
| Object | 60-seat threshold |
—
|
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: 60-seat threshold | Statement: [Democrats approached filibuster-proof majority, thresholdMentioned, 60-seat threshold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thresholdMentioned Context triple: [Democrats approached filibuster-proof majority, thresholdMentioned, 60-seat threshold]
-
A.
thresholdMet
Indicates that a specified limit or condition has been reached or exceeded.
-
B.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
C.
mentions
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
D.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
E.
mentionsSee
Indicates that one entity explicitly refers to or cites another entity within its content.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab7dd5dc8190acabc667a08e6abf |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:29 p.m.