Triple
T11127143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Mayor of Sacramento |
E263169
|
entity |
| Predicate | hasElectedHead |
P981
|
FINISHED |
| Object | Mayor of Sacramento |
—
|
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 of Sacramento | Statement: [Office of the Mayor of Sacramento, hasElectedHead, Mayor of Sacramento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectedHead Context triple: [Office of the Mayor of Sacramento, hasElectedHead, Mayor of Sacramento]
-
A.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
B.
hasConsistentlyElected
Indicates that one entity has regularly and repeatedly chosen or voted for another entity over an extended period or across multiple selection events.
-
C.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
D.
hasLeader
chosen
Indicates that one entity serves as the leader or head of another entity.
-
E.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e82fc5f88190b34c55de3d50f6a7 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.