Triple
T26203641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 New Jersey gubernatorial election |
E655301
|
entity |
| Predicate | republicanPrimaryHeld |
P140433
|
FINISHED |
| Object | 2017-06-06 |
—
|
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: 2017-06-06 | Statement: [2017 New Jersey gubernatorial election, republicanPrimaryHeld, 2017-06-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: republicanPrimaryHeld Context triple: [2017 New Jersey gubernatorial election, republicanPrimaryHeld, 2017-06-06]
-
A.
republicanPrimaryStartDate
Indicates the date on which a Republican Party primary election begins.
-
B.
hadRepublicanPrimary
chosen
Indicates that a Republican Party primary election was held for a given office, race, or jurisdiction.
-
C.
RepublicanPrimaryCandidate
Indicates that an individual is a candidate running in a Republican Party primary election for a particular office.
-
D.
republicanNominee
Indicates that the subject is the officially selected Republican Party candidate for the specified office or election.
-
E.
democraticPrimaryStartDate
Indicates the calendar date on which a specified Democratic Party primary election begins.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdd664c8190862fe9543ab251c9 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:49 p.m.