Triple
T4399181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Senate from North Carolina |
E99569
|
entity |
| Predicate | electionFrequencyPerSeat |
P43028
|
FINISHED |
| Object | Every 6 years |
—
|
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: Every 6 years | Statement: [U.S. Senate from North Carolina, electionFrequencyPerSeat, Every 6 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionFrequencyPerSeat Context triple: [U.S. Senate from North Carolina, electionFrequencyPerSeat, Every 6 years]
-
A.
eachDistrictElects
Indicates that every electoral district selects or chooses its own representative or set of representatives.
-
B.
portionUpForElectionEachCycle
Indicates what fraction of the total membership or seats is contested in each election cycle.
-
C.
constitutionalFrequency
Indicates how often a constitutional or fundamental condition, symptom, or state occurs over a given period.
-
D.
legislativePeriodicity
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
E.
assemblyElectionsHeldEvery
chosen
Indicates that legislative assembly elections are conducted at a regular interval specified by the associated value.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352cc4ab081908bc45d2f76cd4da8 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.