Triple
T357261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas congressional districts |
E7570
|
entity |
| Predicate | apportionmentCycle |
P1678
|
FINISHED |
| Object | decennial census |
—
|
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: decennial census | Statement: [Texas congressional districts, apportionmentCycle, decennial census]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apportionmentCycle Context triple: [Texas congressional districts, apportionmentCycle, decennial census]
-
A.
apportionedBy
Indicates that something is divided or allocated among parts or recipients according to a specified agent, rule, or method.
-
B.
electionCycle
Indicates the recurring period or sequence of time in which elections are organized, conducted, and repeated for a given office or political system.
-
C.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
D.
legislativePeriodicity
chosen
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
E.
electoralAlliancePeriod
Indicates the time span during which two or more political entities are formally joined in an electoral alliance.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebaf0c9881909313f98818e7fa58 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.