Triple
T10454315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas mid-decade redistricting 2003 |
E246510
|
entity |
| Predicate | subjectOfLegislativeWalkout |
P27346
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Texas mid-decade redistricting 2003, subjectOfLegislativeWalkout, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfLegislativeWalkout Context triple: [Texas mid-decade redistricting 2003, subjectOfLegislativeWalkout, true]
-
A.
hasLegislativeSubject
Indicates that a legislative document, action, or body concerns, addresses, or is about a particular subject or topic.
-
B.
legislativeActivity
Indicates involvement in creating, debating, amending, or passing laws or related legislative measures.
-
C.
politicalAct
Indicates that an entity performs, participates in, or is involved with an action related to politics, governance, or public policy.
-
D.
legislatureAffected
chosen
Indicates that an action, event, or measure has an impact on a legislative body or its functioning.
-
E.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe47fee48190b38ec0466ff0165a |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.