Triple
T26689794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Control Funding Formula |
E672844
|
entity |
| Predicate | signingRoleOf |
P21253
|
FINISHED |
| Object | Governor of California |
—
|
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: Governor of California | Statement: [Local Control Funding Formula, signingRoleOf, Governor of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingRoleOf Context triple: [Local Control Funding Formula, signingRoleOf, Governor of California]
-
A.
signatureRole
chosen
Indicates the specific function or capacity in which an entity participates in a signing or signature-related action.
-
B.
signerOf
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
-
C.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
-
D.
signatoryAuthority
Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
-
E.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 3:25 a.m.