Triple
T11574201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erste Kammer |
E274461
|
entity |
| Predicate | opposedChamber |
P39169
|
FINISHED |
| Object | second chamber |
—
|
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: second chamber | Statement: [Erste Kammer, opposedChamber, second chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedChamber Context triple: [Erste Kammer, opposedChamber, second chamber]
-
A.
oppositeChamber
chosen
Indicates that two legislative bodies or chambers are counterparts within the same bicameral system, each serving as the other’s opposite house.
-
B.
oppositionPartyInCongress
Indicates that a political party serves as the primary opposing party to the ruling or majority party within a specific congress or legislative body.
-
C.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
D.
numberOfOpposingVotesInChamber
Indicates the count of votes cast against a proposal or measure within a specific legislative chamber.
-
E.
opposedPoliticalEntity
Indicates that one political entity is in opposition or conflict with another in terms of policies, ideology, or power.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.