Triple
T28602851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey congressional districts |
E723959
|
entity |
| Predicate | startYearOfCurrentConfiguration |
P7746
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [New Jersey congressional districts, startYearOfCurrentConfiguration, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startYearOfCurrentConfiguration Context triple: [New Jersey congressional districts, startYearOfCurrentConfiguration, 2013]
-
A.
settingStartYear
chosen
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
B.
startDateOfCurrentFourYearCyclePattern
Indicates the date on which the currently active four-year recurring cycle begins.
-
C.
startSeasonYear
Indicates the calendar year in which a particular season, series, or recurring event begins.
-
D.
startsYearOn
Indicates that a specified time period or calendar year begins on a particular date or day.
-
E.
specifiedYear
Indicates that a particular year has been explicitly designated or identified in relation to the subject.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 28, 2026, 4:25 a.m.