Triple
T8481334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland municipal elections |
E200525
|
entity |
| Predicate | typicalOfficesContested |
P495
|
FINISHED |
| Object | mayor |
—
|
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: mayor | Statement: [Portland municipal elections, typicalOfficesContested, mayor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOfficesContested Context triple: [Portland municipal elections, typicalOfficesContested, mayor]
-
A.
officeContested
chosen
Indicates that a particular office or position is being actively sought or challenged by multiple parties in an election or selection process.
-
B.
hasOfficeContested
Indicates that an individual has been a candidate for a particular public office in an election.
-
C.
officeContestedLevel
Indicates the degree or intensity to which a particular office or position is being contested or competed for.
-
D.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
E.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5245034819088c7c5c40170c020 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.