Triple
T19318683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles municipal elections |
E483162
|
entity |
| Predicate | nonpartisanByLaw |
P5069
|
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: [Los Angeles municipal elections, nonpartisanByLaw, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonpartisanByLaw Context triple: [Los Angeles municipal elections, nonpartisanByLaw, true]
-
A.
nonPartisan
Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
-
B.
isNonpartisanOffice
chosen
Indicates that the office or position is not affiliated with, controlled by, or contested along formal political party lines.
-
C.
nonVoting
Indicates that an entity participates in a group or organization without possessing the right to vote in its decisions.
-
D.
reasonForNonpartisanship
Indicates that it specifies the reason why an entity is characterized as nonpartisan or not affiliated with any political party.
-
E.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d868dd48190b1439a5f4ff58c48 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.