Triple
T28602829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey congressional districts |
E723959
|
entity |
| Predicate | numberOfDistrictsAfter2000Census |
P1679
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [New Jersey congressional districts, numberOfDistrictsAfter2000Census, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDistrictsAfter2000Census Context triple: [New Jersey congressional districts, numberOfDistrictsAfter2000Census, 13]
-
A.
numberOfDistricts
chosen
Indicates the total count of districts associated with a given entity or area.
-
B.
numberOfDistrictsPeak
Indicates the maximum number of districts that an entity reaches or has at its highest point over a given period or context.
-
C.
numberOfSenateDistricts
Indicates the total count of senate districts associated with a given entity or jurisdiction.
-
D.
eachDistrictElects
Indicates that every electoral district selects or chooses its own representative or set of representatives.
-
E.
modernDistrict
Indicates that one administrative district is the contemporary or current counterpart of another, typically older or historical, district.
- 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_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: April 28, 2026, 4:25 a.m.