Triple
T21097507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Irish presidential election |
E519805
|
entity |
| Predicate | isContested |
P140434
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [2004 Irish presidential election, isContested, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContested Context triple: [2004 Irish presidential election, isContested, false]
-
A.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
resultContested
chosen
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
D.
hasOfficeContested
Indicates that an individual has been a candidate for a particular public office in an election.
-
E.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5a3a9481908e30fba9717dc461 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:52 p.m.