Triple
T27675528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 Maryland gubernatorial election |
E697767
|
entity |
| Predicate | endedPartyControl |
P110013
|
FINISHED |
| Object | Democratic Party |
—
|
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: Democratic Party | Statement: [2002 Maryland gubernatorial election, endedPartyControl, Democratic Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedPartyControl Context triple: [2002 Maryland gubernatorial election, endedPartyControl, Democratic Party]
-
A.
endedControlOf
chosen
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
B.
regulatedParty
Indicates that one entity is subject to rules, oversight, or control imposed by another regulating entity.
-
C.
endedParticipationOf
Indicates that one entity caused or marked the termination of another entity’s involvement in an activity, event, or relationship.
-
D.
decliningParty
Indicates that an entity refuses, rejects, or turns down an offer, request, or proposal made by another entity.
-
E.
hasOtherParty
Indicates that an entity is associated with another distinct party involved in the same relationship, transaction, or interaction.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:43 p.m.