Triple
T10939504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Babick |
E258427
|
entity |
| Predicate | politicalOfficeScope |
P38306
|
FINISHED |
| Object | local government |
—
|
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: local government | Statement: [Steve Babick, politicalOfficeScope, local government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalOfficeScope Context triple: [Steve Babick, politicalOfficeScope, local government]
-
A.
topPoliticalOffice
Indicates that the subject holds or is associated with the highest-ranking political office within a given governmental or political system.
-
B.
politicalOfficeJurisdiction
Indicates the governmental area or jurisdiction over which a political office holds authority or responsibility.
-
C.
hasPoliticalOfficeScope
chosen
Indicates that a political office or position is limited to, defined within, or applicable to a specific jurisdiction, level, or scope of political authority.
-
D.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
E.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770c1389881909341170984211810 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.