Triple
T1582912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insurance Commissioner of California |
E34005
|
entity |
| Predicate | officeBecameElectiveYear |
P29569
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Insurance Commissioner of California, officeBecameElectiveYear, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeBecameElectiveYear Context triple: [Insurance Commissioner of California, officeBecameElectiveYear, 1991]
-
A.
selectionYear
Indicates the year in which an entity was chosen or selected for a particular role, status, or inclusion.
-
B.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
-
D.
targetedOfficeElectionYear
chosen
Indicates the year in which the election is held for the office that is the target of the relationship.
-
E.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.