Triple
T137077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congressional Research Service |
E2769
|
entity |
| Predicate | nonpartisan |
P6897
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Congressional Research Service, nonpartisan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonpartisan Context triple: [Congressional Research Service, nonpartisan, true]
-
A.
nonPartisan
chosen
Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
-
B.
isNonpartisanOffice
Indicates that the office or position is not affiliated with, controlled by, or contested along formal political party lines.
-
C.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.