Triple
T25105876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Seaborn |
E628865
|
entity |
| Predicate | runsForOfficeIn |
P75922
|
FINISHED |
| Object | California 47th Congressional District |
—
|
NE NERFINISHED |
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: California 47th Congressional District | Statement: [Sam Seaborn, runsForOfficeIn, California 47th Congressional District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsForOfficeIn Context triple: [Sam Seaborn, runsForOfficeIn, California 47th Congressional District]
-
A.
nominatedForOffice
Indicates that an entity has been formally put forward as a candidate to hold a particular office or position.
-
B.
ranInElection
Indicates that an entity was a candidate participating in a specific election.
-
C.
campaignForOffice
chosen
Indicates that an individual is actively seeking election to a public office or position through an organized political campaign.
-
D.
announcedCandidacyFor
Indicates that an entity has publicly declared their intention to run as a candidate for a specific position, office, or role.
-
E.
electionForOffice
Indicates that an election event is held to select or fill a specific office or position.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4656fe058819084a69c49783cc36d |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:26 a.m.