Triple
T31688729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamaican general election, 2007 |
E808728
|
entity |
| Predicate | contestingParty |
P29573
|
FINISHED |
| Object | Jamaica Labour 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: Jamaica Labour Party | Statement: [Jamaican general election, 2007, contestingParty, Jamaica Labour Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestingParty Context triple: [Jamaican general election, 2007, contestingParty, Jamaica Labour Party]
-
A.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
B.
challengerParty
chosen
Indicates the political party that is opposing or seeking to unseat an incumbent or dominant party in a given contest or election.
-
C.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
-
D.
contestedAs
Indicates that one entity challenges, disputes, or competes for the status, claim, or position held by another entity.
-
E.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 30, 2026, 11:07 p.m.