Triple
T14994479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate of Bremen |
E373920
|
entity |
| Predicate | hasCabinetMemberRank |
P57228
|
FINISHED |
| Object | Senator |
—
|
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: Senator | Statement: [Senate of Bremen, hasCabinetMemberRank, Senator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabinetMemberRank Context triple: [Senate of Bremen, hasCabinetMemberRank, Senator]
-
A.
hasMinisterialRank
chosen
Indicates that an entity holds a position or status equivalent to a government minister in rank.
-
B.
servedInCabinetOf
Indicates that one person held a position as a member of the governmental cabinet led by another person.
-
C.
hasGubernatorialMember
Indicates that an entity has, as part of its composition or governance, a member who holds or has held the office of governor.
-
D.
notableCabinetMember
Indicates that a person has served as a particularly prominent or significant member of a government cabinet.
-
E.
hasMinister
Indicates that one entity serves as the minister (political, religious, or administrative official) responsible for or associated with another entity.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded716ebb481908224d2d4f7561b03 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.